CVE-2026-41139: Unsafe array index getter in mathjs
Math.js is an extensive math library for JavaScript and Node.js. From version 13.1.0 to before version 15.2.0, arbitrary JavaScript can be executed via the expression parser of mathjs. This issue has been patched in version 15.2.0.
Security readout for executives and security teams
Plain-English summary
CVE-2026-41139 affects mathjs, a JavaScript math library. Vulnerable versions can let an attacker execute arbitrary JavaScript through the expression parser. This can threaten confidentiality, integrity, and availability when vulnerable parsing is exposed to users or lower-privileged actors.
Executive priority
Prioritize remediation this cycle for any service that exposes mathjs expression parsing to users, tenants, or API clients. The issue has high impact and a patched version is named. Lower priority may be reasonable only where mathjs is absent, unused, or not reachable by untrusted input.
Technical view
mathjs versions 13.1.0 through before 15.2.0 are affected. The CVE describes arbitrary JavaScript execution via the expression parser, with CWE-94 and CWE-915 mappings. CVSS 3.0 is 8.8: network vector, low complexity, low privileges, no user interaction, and high impact across CIA.
Likely exposure
Applications using mathjs >=13.1.0 and <15.2.0 are potentially exposed, especially if they evaluate user-controlled expressions. Exposure can be direct or transitive through npm dependencies. The source bundle does not identify specific downstream products or platforms beyond mathjs.
Exploitation context
The CVE is not marked KEV, and the provided sources do not state active exploitation. The CVSS vector indicates a remotely reachable, low-complexity issue requiring low privileges and no user interaction. Treat exposed expression parsing as urgent, but do not assume exploitation without local evidence.
Researcher notes
Focus triage on parser reachability, trust boundaries, and deployed versions. The sources confirm affected range and fixed release but do not provide safe compensating controls beyond updating. Avoid relying on exploit claims unless supported by KEV, vendor advisories, or observed telemetry.
Mitigation direction
Upgrade mathjs to version 15.2.0 or later.
Audit lockfiles for direct and transitive vulnerable mathjs versions.
Restrict untrusted access to expression parsing until upgraded.
Review vendor guidance for packaged or downstream distributions.
Prioritize internet-facing or multi-tenant expression evaluation paths.
Validation and detection
Check package manifests and lockfiles for mathjs versions.
Confirm deployed artifacts use mathjs 15.2.0 or later.
Identify routes or jobs evaluating user-controlled expressions.
Review dependency trees for transitive mathjs inclusion.
Check Red Hat status if using Red Hat-distributed packages.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-915: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.