dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2026-24822

CRITICAL · 10.0 CVSS v4.0 Published 2026-01-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds Write, Heap-based Buffer Overflow vulnerability in ttttupup wxhelper (src modules). This vulnerability is associated with program files mongoose.C. This issue affects wxhelper: through 3.9.10.19-v1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Heap-based buffer overflow in mongoose.c within wxhelper allows out-of-bounds write operations. The vulnerability exists in the src modules of wxhelper up to version 3.9.10.19-v1, potentially allowing attackers to corrupt heap memory and execute arbitrary code.

MitigationUpdate wxhelper to a version beyond 3.9.10.19-v1 once available, or apply vendor-provided patch to fix bounds checking in mongoose.c. If immediate update is not possible, restrict network access to the affected service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:D/RE:M/U:Red

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate wxhelper installation and version
    Search for wxhelper executables, libraries, or installed packages on the system. Common locations include /usr/local/, /opt/, or program directories. Check for version information in file metadata, --version output, or package manager listings.
    Affected if wxhelper version is 3.9.10.19-v1 or earlier (any version up to and including 3.9.10.19-v1)
  2. Identify mongoose.c component presence
    Search for the mongoose source file (mongoose.c) or compiled mongoose library within the wxhelper installation directory. Look for files named mongoose.c, mongoose.h, libmongoose, or similar web server components.
    Affected if mongoose.c module exists within the wxhelper installation
  3. Verify mongoose HTTP server functionality is enabled
    Check wxhelper configuration files, startup scripts, or runtime settings to determine if the built-in HTTP server (provided by mongoose) is actively used or exposed. Review config files for HTTP server ports, web interface settings, or remote administration features.
    Affected if HTTP server functionality in wxhelper is enabled or configured to run
  4. Confirm version falls within affected range
    Compare the installed wxhelper version number against the affected range (versions up to and including 3.9.10.19-v1). Use package version queries, binary metadata, or vendor documentation to obtain exact version string.
    Affected if Installed version is 3.9.10.19-v1 or any earlier version of wxhelper

A user is affected if wxhelper with mongoose.c component is installed and the version is 3.9.10.19-v1 or earlier, with the HTTP server feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Update wxhelper to a version beyond 3.9.10.19-v1 once available, or apply vendor-provided patch to fix bounds checking in mongoose.c. If immediate update is not possible, restrict network access to the affected service.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24822 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24822 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data