Categories
CVE-2026-32640 critical CVSS 9.8

Code Injection in simpleeval (CVE-2026-32640)

Summary

Code injection in simpleeval (CVE-2026-32640). Successful exploitation can lead to full system takeover. Exploitable via names. Mitigation: upgrade to 1.0.5 or later.

Original description

The description as published by the source.

Impact

If the objects passed in as names to SimpleEval have modules or other disallowed / dangerous objects available as attrs.
Additionally, dangerous functions or modules could be accessed by passing them as callbacks to other safe functions to call.

Examples (found by @ByamB4):

Any module where non-underscore attribute chains reach os or sys:

  • os.path, pathlib, shutil, glob (direct .os / .sys attributes)
  • statistics (has .sys)
  • numpy (has .ctypeslib.os and .f2py.sys)
  • urllib.parse (has .warnings.sys)

Patches

The latest version 1.0.5 has this issue fixed.

Workarounds

Don't pass in objects or modules which have direct attributes to potentially dangerous items.
Use a wrapper to wrap the potentially vulnerable items (See the ModuleWrapper in version 1.0.5)

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-32640 has been found in simpleeval.
Attackers can target a specific entry point like names over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.8/10.
What to do: upgrade simpleeval to 1.0.5 or later.
If unsure, ask your IT team or search "simpleeval CVE-2026-32640" on the vendor's site.

CVE-2026-32640 (simpleeval) — CWE-94 / CVSS v3 9.8
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: names
Patched: 1.0.5 — apply immediately
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

Arbitrary code execution (CWE-94) exists in simpleeval. Attackers reach the vulnerable code path via names without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of simpleeval. Attack surface: names.

🔥 Severity

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

🔧 How to fix

Update to 1.0.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'simpleeval' . 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 'simpleeval' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade simpleeval to 1.0.5

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

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

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

Affected packages

PyPI simpleeval
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.5"}]}]
pip simpleeval
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.5"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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