Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-41139 high CVSS 8.8

Vulnerability in mathjs (CVE-2026-41139)

Summary

Vulnerability in mathjs (CVE-2026-41139). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 15.2.0 or later.

Original description

The description as published by the source.

Impact

This security vulnerability allowed executing arbitrary JavaScript via the expression parser of mathjs. You can be affected when you have an application where users can evaluate arbitrary expressions using the mathjs expression parser.

Patches

The issue was introduced in mathjs v13.1.0, and patched in mathjs v15.2.0.

Workarounds

There is no workaround without upgrading to v15.2.0.

References

You can find out more via the commit fixing this issue: https://github.com/josdejong/mathjs/commit/24d5ee7e25e85d49619b09122f055db4139bc057 (part of PR https://github.com/josdejong/mathjs/pull/3656).

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-41139 has been found in mathjs.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade mathjs to 15.2.0 or later.
If unsure, ask your IT team or search "mathjs CVE-2026-41139" on the vendor's site.

CVE-2026-41139 (mathjs) — CWE-915 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 15.2.0 — apply immediately
Workaround: There is no workaround without upgrading to v15.2.0.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-915) exists in mathjs.

📍 Affected scope

Check the vendor advisory for the affected versions of mathjs.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 15.2.0.

🛡️ Workaround

Workaround: There is no workaround without upgrading to v15.2.0.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mathjs' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'mathjs' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mathjs を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There is no workaround without upgrading to `v15.2.0`.

    パッチが適用されるまでの応急処置として、There is no workaround without upgrading to v15.2.0. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade mathjs to 15.2.0

    ステージング環境で 15.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm mathjs
[{"type":"SEMVER","events":[{"introduced":"13.1.0"},{"fixed":"15.2.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details