LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32640: (SimpleEval) Objects (including modules) can leak dangerous modules through to direct access inside the sandbox.

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.

HighCVSS 8.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SimpleEval lets applications evaluate limited Python-like expressions. Before 1.0.5, objects supplied to the sandbox could expose dangerous modules or functions, weakening the sandbox boundary. Business risk is highest where SimpleEval evaluates user-controlled expressions or untrusted users influence callback inputs.

Executive priority

Treat as high priority where expression evaluation is exposed to users or external data. Patch promptly, then verify application code is not passing sensitive objects into evaluators.

Technical view

The issue affects danthedeckie/simpleeval versions before 1.0.5. Object attributes and callbacks could provide direct access to disallowed modules or dangerous functions inside the evaluator. The CVE maps to CWE-915 and CWE-94 and carries CVSS 4.0 score 8.7 with network, low-complexity, no-auth characteristics.

Likely exposure

Python applications using simpleeval below 1.0.5, especially API, automation, rules, templating, or workflow features that evaluate expressions from users, tenants, or external data.

Exploitation context

The provided sources do not show KEV listing or confirmed active exploitation. The described bug is sandbox escape risk when unsafe objects, modules, attributes, or callbacks are reachable through values passed into SimpleEval.

Researcher notes

Evidence supports a sandbox boundary weakness fixed in 1.0.5. The bundle does not include exploit details or active exploitation evidence. Focus validation on dependency reachability and evaluator inputs rather than assuming every installation is remotely exploitable.

Mitigation direction

  • Upgrade simpleeval to version 1.0.5 or later.
  • Rebuild and redeploy services that vendor or bundle simpleeval.
  • Review downstream Debian or Red Hat advisories where packages are OS-managed.
  • Reduce exposed names, objects, modules, and callbacks passed into evaluators.
  • Add dependency controls to prevent reintroducing simpleeval versions below 1.0.5.

Validation and detection

  • Inventory Python dependencies, lockfiles, SBOMs, and container images for simpleeval.
  • Confirm every deployed simpleeval instance is version 1.0.5 or later.
  • Identify code paths calling SimpleEval or simple_eval with external input.
  • Review supplied names and callbacks for objects exposing sensitive attributes.
  • Check vendor package status if using Debian or Red Hat builds.
Prepared
Confidence
high
Sources
9

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.

Open ATT&CK lookup
cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32640 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
3ADP providers
8Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NGitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2026-32640Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
redhat-SADPsimpleeval: SimpleEval: Arbitrary code execution via sandbox escape due to improper object handling
other:Red Hat severity ratingcvssV3_1
  • 2026-03-13T22:02:17.336Z: Reported to Red Hat.
  • 2026-03-13T21:03:53.435Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
danthedeckiesimpleeval< 1.0.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-915 · source CWE mapping

Improperly Controlled Modification of Dynamically-Determined Object Attributes

Improperly Controlled Modification of Dynamically-Determined Object Attributes represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.