CVE
yt code injection via eval() in HDF5 file parsing
Affects yt 4.4.4 and earlier, and the main branch through commit e94f0cc, when a crafted ytdata HDF5 file is opened with yt.load(). No fixed version is listed.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. yt 4.4.4 or earlier, and the main branch through commit e94f0cc A victim opens a crafted ytdata HDF5 file with yt.load()
Summary
The yt software from yt-project contains a code injection flaw in how it reads ytdata HDF5 files: a crafted con_args attribute is passed unchecked to eval(). A local attacker with no login can get a user to load a malicious .h5 file with yt.load(), which runs attacker-supplied Python code with that user's privileges.
Original description
yt through 4.4.4 contains a code injection vulnerability that allows attackers to execute Python code by supplying a crafted con_args attribute in a ytdata HDF5 file. SavedDataset._parse_parameter_file() passes con_args to eval() unrestricted, so loading a malicious .h5 file with yt.load() runs attacker code as the user.
Who should check
Anyone running yt 4.4.4 or earlier who opens ytdata .h5 datasets received, downloaded or shared with yt.load()
“Affected versions: <= 4.4.4 (and main through e94f0cc )”
cve.now Index
- 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
What to do
Check whether your setup matches what the bug needs.
yt 4.4.4 or earlier, and the main branch through commit e94f0cc A victim opens a crafted ytdata HDF5 file with yt.load()Apply the patch listed under Evidence.
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-132751 (yt through 4.4.4 Code Injection via con_args eval() in ytdata HDF5), 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-132751 (entry last updated 2026-11-18):
Affected:
- PyPI package yt: through 4.4.4
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- yt 4.4.4 or earlier, and the main branch through commit e94f0cc (source: https://github.com/yt-project/yt/issues/5641)
- A victim opens a crafted ytdata HDF5 file with yt.load() (source: https://github.com/yt-project/yt/issues/5641)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-132751 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132751 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/yt-project/yt/commit/ce997aebb89423a6f5d86c3bda24094e908d3c2d
- https://github.com/yt-project/yt/issues/5641
- https://github.com/yt-project/yt/blob/yt-4.4.4/yt/frontends/ytdata/data_structures.py#L52-L56
- https://www.vulncheck.com/advisories/yt-through-4.4.4-code-injection-via-con-args-eval-in-ytdata-hdf5
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-132751
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-132751"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- ytPyPI
through 4.4.4
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132751 |
| Record | NVD · CVE-2026-132751 |
| Other links 4 | |
| Patch | GitHub · yt-project/yt · Commit ce997aeb |
| Report | GitHub · yt-project/yt · Issue #5641 |
| Repository | GitHub · yt-project/yt · yt/frontends/ytdata/data_structures.py · L52-L56 |
| Link | vulncheck.com · advisories/yt-through-4.4.4-code-injection-via-con-args-eval-in-ytdata-hdf5 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132751
Is CVE-2026-132751 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?
Opening an attacker-supplied ytdata dataset with yt.load() runs arbitrary Python code as the user. The code runs with the user's own privileges on the analysis machine, including file access and credentials.Source: github.com
Which versions are affected by CVE-2026-132751?
yt (PyPI): through 4.4.4.Source: cve.now feed data
Am I affected, and how do I check?
Versions 4.4.4 and earlier are affected, as is the main branch through commit e94f0cc. To check a installed copy, look at the yt version reported by Python's import of yt. The bug involves loading ytdata HDF5 files with yt.load().Source: github.com
How do I fix CVE-2026-132751?
The checked facts name no fixed version or vendor patch. Avoid opening ytdata HDF5 files from untrusted sources with yt.load() until a fix is confirmed.Source: github.com