Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.3

weixin4j has Improperly Controlled Sequential Memory Allocation

CVE-2026-24819GHSA-444m-px7r-qpvv

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven com.foxinmy:weixin4j-base

    Affected
    <= 1.10.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2026-24819: 0.44% estimated exploitation activity in the next 30 days; percentile 38.19 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-444m-px7r-qpvv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-24819

Advisory: weixin4j has Improperly Controlled Sequential Memory Allocation
IDs: CVE-2026-24819, GHSA-444m-px7r-qpvv
Record: https://patchnext.com/advisories/cve-2026-24819 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.foxinmy:weixin4j-base: affected <= 1.10.2

## Suggested inspection (read-only)
- Maven com.foxinmy:weixin4j-base: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.foxinmy:weixin4j-base.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-444m-px7r-qpvv (GitHub-reviewed advisory GHSA-444m-px7r-qpvv lists affected ranges: Maven com.foxinmy:weixin4j-base >=0 <=1.10.2)

Commands are suggestions: review each one before running it.

Loading voting…