CVE-2026-24819: weixin4j Improperly Controlled Sequential Memory Allocation Vulnerability

com.foxinmy:weixin4j-base Updated 28 Jan 2026

Summary

27/01/2026
No i
Moderate
6.3

CVE-2026-24819: weixin4j has Improperly Controlled Sequential Memory Allocation. Affects com.foxinmy:weixin4j-base versions < 1.10.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

weixin4j is an open-source Java library designed for integrating with WeChat's API, providing functionalities such as messaging, user management, and more. The library is widely used in applications that require interaction with WeChat services. However, it has been found to have a vulnerability related to memory allocation that could potentially lead to security issues.

Vulnerability Detail

The vulnerability identified as CVE-2026-24819 in weixin4j arises from improperly controlled sequential memory allocation within the library's codebase, specifically in the CharArrayBuffer.Java and ClassUtil.Java files. This flaw can lead to memory corruption, allowing attackers to exploit the application by manipulating memory allocation patterns. The issue affects all versions of weixin4j up to 1.10.2, making it critical for users to address this vulnerability to prevent potential exploitation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can limit the use of the affected functionalities in your application until you can apply the patch. Ensure that you monitor memory allocation closely and avoid using features that rely on the vulnerable components.

Conclusion

The CVE-2026-24819 vulnerability in the weixin4j library poses a significant risk due to improperly controlled memory allocation. Users are advised to update to the patched version to mitigate potential security threats. Monitoring tools like Vulert can assist in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for com.foxinmy:weixin4j-base →

Share this vulnerability

FAQ

CVE-2026-24819 is a vulnerability in the weixin4j library that involves improperly controlled sequential memory allocation, which can lead to memory corruption.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If exploited, this vulnerability could allow attackers to manipulate memory allocation, potentially leading to application crashes or unauthorized access to sensitive data.

Yes, a patch is available in version 1.10.3 of the weixin4j-base package. It is recommended to update to this version or later.

The CVSS score for CVE-2026-24819 is 6.3, indicating a moderate severity level.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback