How severe is CVE-2026-32640?

No CVSS score has been assigned to CVE-2026-32640 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-32640?

CVE-2026-32640 affects the following packages: simpleeval (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-32640?

Update simpleeval to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32640 is resolved across your whole dependency graph.

How do I detect CVE-2026-32640 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simpleeval, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-32640 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2026-32640 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-32640 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-32640?

CVE-2026-32640 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 49th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-32640?

CVE-2026-32640 is classified as Code Injection (CWE-94), CWE-915 (CWE-915). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-32640 published, and has it been updated?

CVE-2026-32640 was published on March 13, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-32640 — simpleeval

CVE-2026-32640 is a Code Injection vulnerability in simpleeval. A fix is available for simpleeval — see the affected versions and patch details below.

(SimpleEval) Objects (including modules) can leak dangerous modules through to direct access inside the sandbox.

Also known asGHSA-44vg-5wv2-h2hgPYSEC-2026-132

Published

Mar 13, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32640.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍simpleeval

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`simpleeval`	all versions	1.0.5`pip install --upgrade 'simpleeval==1.0.5'`

Affected Products

1 product · 1 configurations

Application

simpleevaldanthedeckie

< 1.0.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simpleeval, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simpleeval to 1.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32640 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift AI 2.25	`rhoai/odh-training-cuda121-torch24-py311-rhel9:1776243258`	RHSA-2026:10184
Red Hat OpenShift AI 3.3	`rhoai/odh-trustyai-nemo-guardrails-server-rhel9:1782471606`	RHSA-2026:37275

UbuntuHIGH

USN-8301-1Ubuntu

Frequently Asked Questions

### 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 Do

O3 Security · Impact-Aware SCA

Is CVE-2026-32640 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works