How severe is CVE-2026-24819?

No CVSS score has been assigned to CVE-2026-24819 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-24819?

CVE-2026-24819 affects the following packages: com.foxinmy:weixin4j-base (Maven). Ecosystems affected: Maven.

How do I fix CVE-2026-24819?

The records we use list no patched version of com.foxinmy:weixin4j-base for CVE-2026-24819. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2026-24819 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.foxinmy:weixin4j-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-24819 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2026-24819 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-24819 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-24819?

CVE-2026-24819 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-24819?

CVE-2026-24819 is classified as CWE-1325 (CWE-1325). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-24819 published, and has it been updated?

CVE-2026-24819 was published on January 27, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2026-24819 — weixin4j-base

Fix: foxinmy/weixin4j#229

CVE-2026-24819 is a CWE-1325 vulnerability in com.foxinmy:weixin4j-base. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

weixin4j has Improperly Controlled Sequential Memory Allocation

Published

Jan 27, 2026

Updated

Feb 3, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-24819.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.foxinmy:weixin4j-base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

This issue affects all versions of weixin4j. A path is available: d1c8258

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.foxinmy:weixin4j-base`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.foxinmy:weixin4j-base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of com.foxinmy:weixin4j-base for CVE-2026-24819. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Improperly Controlled Sequential Memory Allocation vulnerability in foxinmy weixin4j (weixin4j-base/src/main/java/com/foxinmy/weixin4j/util modules). This vulnerability is associated with program files CharArrayBuffer.Java, ClassUtil.Java. This issue affects all versions of weixin4j. A path is available: [d1c8258](https://github.com/foxinmy/weixin4j/commit/4b7ad14df6567064b468b4c9cb7a8bfeff48c8bd)

O3 Security · Impact-Aware SCA

Is CVE-2026-24819 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works