# CVE-2026-24819: An out-of-memory (OOM) issue in foxinmy/weixin4j

> An out-of-memory vulnerability in the weixin4j library allows attackers to cause a denial of service through improper memory allocation.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/AU:Y/R:A/V:D/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2026
- **Updated:** 27 Jan 2026
- **Also known as:** GHSA-444m-px7r-qpvv

## What is CVE-2026-24819?

CVE-2026-24819 is a medium-severity denial of service vulnerability in foxinmy weixin4j, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 weixin4j.

Weakness: CWE-1325 (Improperly Controlled Sequential Memory Allocation)

## Which versions are affected by CVE-2026-24819?

2 open source packages ship an affected version, including com.foxinmy:weixin4j-base.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.foxinmy:weixin4j-base` | Maven | All versions to 1.10.2 | None |
| `com.foxinmy:weixin4j-base` | Maven | All versions to 1.10.2 | None |

## How do I fix CVE-2026-24819?

No fix has been published for CVE-2026-24819 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24819 being exploited?

There is no known exploitation of CVE-2026-24819 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24819 and fix it if it is affected.

What it is: CVE-2026-24819 is a medium-severity denial of service vulnerability in foxinmy weixin4j, published on 27 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24819 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.foxinmy:weixin4j-base (Maven): affected all versions up to 1.10.2; no fix listed
- com.foxinmy:weixin4j-base (Maven): affected all versions up to 1.10.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24819/ (Markdown: https://insights.sbomify.com/CVE-2026-24819/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24819
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24819
- OSV: https://osv.dev/vulnerability/CVE-2026-24819

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24819/
Summaries are generated and may contain mistakes; the official description above is the record.