dbcve.org
SimpleevalApplication · Danthedeckie

CVE-2026-32640

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1.0.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
SimpleEval is a library for adding evaluatable expressions into python projects. Prior to 1.0.5, objects (including modules) can leak dangerous modules through to direct access inside the sandbox. If the objects you've 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. The latest version 1.0.5 has this issue fixed. This vulnerability is fixed in 1.0.5.

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 confidence

SimpleEval before 1.0.5 suffers from a sandbox escape vulnerability where dangerous Python modules and functions can leak through objects passed as names to the expression evaluator. Attackers can access disallowed modules via object attributes or by passing dangerous functions as callbacks to safe functions, potentially achieving arbitrary code execution.

MitigationUpgrade SimpleEval to version 1.0.5 or later. Additionally, audit all objects passed into SimpleEval to ensure they do not expose dangerous attributes or modules.

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
SimpleevalApplication
Affected:< 1.0.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SimpleEval version
    Run 'pip show simpleeval' or import simpleeval and print(simpleeval.__version__)
    Affected if Version is below 1.0.5
  2. Identify code using simpleeval.eval()
    Search codebase for 'simpleeval.eval' or 'SimpleEval().eval' calls to find where expressions are being evaluated
    Affected if Code passes user-controlled expressions to eval() without sanitization
  3. Inspect objects passed to evaluator
    Review all objects passed as 'names', 'functions', or in the 'parent' scope to eval(); examine their __dict__ and __class__ attributes for dangerous items like __import__, os, sys, subprocess, or open
    Affected if Objects passed to SimpleEval expose dangerous modules or functions as accessible attributes
  4. Check for callback function exposure
    Look for code that passes custom functions to SimpleEval via the 'functions' parameter; audit these functions for unsafe operations
    Affected if Callbacks provided to SimpleEval allow access to dangerous Python capabilities

You are affected if SimpleEval version is below 1.0.5 AND your code passes objects or callbacks to the evaluator that expose dangerous Python modules, functions, or system capabilities.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.5 or later
Fixed in 1.0.5
Interim mitigation

Upgrade SimpleEval to version 1.0.5 or later. Additionally, audit all objects passed into SimpleEval to ensure they do not expose dangerous attributes or modules.

Recommended fix High confidence

1.0.5

  1. Check current SimpleEval version: pip show simpleeval
  2. Upgrade to the fixed version: pip install simpleeval==1.0.5
  3. Verify the upgrade was successful: pip show simpleeval

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Simpleeval Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32640 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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