Skip to main content
Menu
CVEs

diffpy.structure code execution via eval in CIF symmetry parsing

Affects diffpy.structure 3.5.0 and earlier when parsing CIF files with symmetry operations in the _space_group_symop_operation_xyz loop. Fixed in 3.5.1.

CVE-2026-133708Published , updated

8.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 3.5.1
Who is exposed
Specific setups only

Summary

diffpy.structure, a Python package, is affected by a code execution flaw in how it parses CIF files. An attacker can craft a CIF file with malicious symmetry operations that the software passes to eval(), running Python code with the victim's privileges. This requires local access and a user to open the crafted file.

Written by a model

Original description

diffpy.structure before 3.5.1 contains a code execution vulnerability that allows attackers to run Python code by supplying crafted CIF symmetry operations passed to eval() in get_symop(). Attackers can embed expressions in the _space_group_symop_operation_xyz or _symmetry_equiv_pos_as_xyz loop to execute code with victim privileges when the CIF file is parsed locally.

Who should check

Teams and researchers using diffpy.structure 3.5.0 or earlier to parse CIF files from collaborators, downloads, structure databases or paper supplements.

“Affected versions: <= 3.5.0”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    diffpy.structure version 3.5.0 or earlier is affected A CIF file with a symmetry operation in the _space_group_symop_operation_xyz loop is parsed The CIF block contains _atom_site_label so it is parsed as a structure
  2. Upgrade to a fixed version: 3.5.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133708 (diffpy.structure before 3.5.1 Code Execution via eval in get_symop CIF Parsing), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133708 (entry last updated 2026-11-20):
Affected:
- PyPI package diffpy.structure: fixed in 3.5.1
Fixed versions: 3.5.1.
Vendor patches: f4be1d5 (source: https://github.com/diffpy/diffpy.structure/commit/f4be1d534fa9cf488c8e83f258e59fe09b526f62). Check each asset for these patch ids, not only its version.
Conditions (all must be true for the bug to be hit):
- diffpy.structure version 3.5.0 or earlier is affected (source: https://github.com/diffpy/diffpy.structure/issues/204)
- A CIF file with a symmetry operation in the _space_group_symop_operation_xyz loop is parsed (source: https://github.com/diffpy/diffpy.structure/issues/204)
- The CIF block contains _atom_site_label so it is parsed as a structure (source: https://github.com/diffpy/diffpy.structure/issues/204)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-133708 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133708 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/diffpy/diffpy.structure/commit/f4be1d534fa9cf488c8e83f258e59fe09b526f62
- https://github.com/diffpy/diffpy.structure/issues/204
- https://github.com/diffpy/diffpy.structure/blob/3.5.0/src/diffpy/structure/parsers/p_cif.py
- https://github.com/diffpy/diffpy.structure/releases/tag/3.5.1
- https://www.vulncheck.com/advisories/diffpy-structure-before-3.5.1-code-execution-via-eval-in-get-symop-cif-parsing
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133708
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133708"}.

Affected versions

cve.now Index

24Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach10/20Affects PyPI packages
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 34 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 7

Questions about CVE-2026-133708

Is CVE-2026-133708 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The CIF parser passes symmetry operation text from the _space_group_symop_operation_xyz loop to Python eval(), so a crafted CIF file can run the file author's Python code with the privileges of the user parsing it.

Source: github.com, github.com

Which versions are affected by CVE-2026-133708?

diffpy.structure (PyPI): before 3.5.1.

Source: cve.now feed data

Am I affected, and how do I check?

diffpy.structure version 3.5.0 or earlier is affected when a CIF block containing _atom_site_label is parsed as a structure and includes a _space_group_symop_operation_xyz entry. To check a version, run pip show diffpy.structure or print diffpy.structure.__version__ in Python.

Source: github.com, github.com

How do I fix CVE-2026-133708?

Upgrade diffpy.structure to 3.5.1, which changes get_symop so it no longer evaluates CIF symmetry operations (patch f4be1d5).

Source: github.com, github.com

No corrections so far. Something wrong on this page? Report an error.