CVE-2026-41507
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 · uneditedmath-codegen generates code from mathematical expressions. Prior to version 0.4.3, string literal content passed to cg.parse() is injected verbatim into a new Function() body without sanitization. This allows an attacker to execute arbitrary system commands when user-controlled input reaches the parser. Any application exposing a math evaluation endpoint where user input flows into cg.parse() is vulnerable to full RCE. This issue has been patched in version 0.4.3.
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 · high confidenceThe math-codegen library before version 0.4.3 has a code injection vulnerability where user input passed to cg.parse() is directly embedded into a JavaScript Function() constructor without any sanitization, allowing arbitrary code execution and full RCE.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.4.3CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed version of math-codegenRun 'npm list math-codegen' or 'yarn list math-codegen' to see the currently installed version. Alternatively, check package.json for the math-codegen dependency version.Affected if The installed version is less than 0.4.3 (e.g., 0.4.2, 0.4.1, 0.4.0, or any version before 0.4.3)
-
Identify if math-codegen is imported in your codebaseSearch your codebase for 'require("math-codegen")' or 'import * as cg from "math-codegen"' or similar import statements.Affected if The library is imported and used in your application
-
Find all usages of cg.parse() functionSearch your codebase for '.parse(' calls on math-codegen (e.g., 'cg.parse(', 'mathCodegen.parse(') to locate where the vulnerable function is invoked.Affected if cg.parse() is called anywhere in your codebase
-
Trace if user input reaches cg.parse()Review the code paths around each cg.parse() call and determine if data from HTTP requests, user forms, API parameters, files, or other untrusted sources flows into the parse() function.Affected if User-controlled input (request parameters, body data, file contents, etc.) is passed directly to cg.parse() without validation or sanitization
-
Verify the vulnerable pattern existsExamine the specific cg.parse() call and confirm the input is passed directly to the function without passing through a validation or sanitization layer first.Affected if The user input is passed directly to cg.parse() without any transformation or validation that would prevent code injection
You are affected if math-codegen version is below 0.4.3 AND your application passes untrusted user input directly into the cg.parse() function, enabling arbitrary code execution.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped0.4.3
Upgrade math-codegen to version 0.4.3 or later. Audit all code paths where user input flows into cg.parse() and implement input validation as a defense-in-depth measure.
math-codegen 0.4.3
- Upgrade math-codegen to version 0.4.3 or later using your package manager (e.g., npm install [email protected] or npm install math-codegen@latest)
- After upgrading, verify that user-controlled input is no longer passed directly to cg.parse() without sanitization
- Test the application to ensure the fix resolves the vulnerability without breaking existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41507 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41507 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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