cve.bz

CVE-2026-120499 h5io h5io: Eval Injection

8.5 highEPSS 0.4%

High (8.5) in h5io h5io. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
h5io before 0.2.6 contains a code injection vulnerability in read_hdf5() that allows attackers to execute arbitrary code by supplying a crafted HDF5 file. Attackers can store Python code in a node titled timezone, which _triage_read() passes to eval() with builtins reachable, name an arbitrary module in class or custom-object nodes that _import_class() imports, or place pickled objects in pd_dataframe or pd_series nodes that pandas deserializes on read.

Severity

CVSS 4.0

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

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-95 Improper Neutralization of Directives in Dynamically Evaluated Code (Eval Injection)
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A05:2025 Injection, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-120499 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120499?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120499?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120499 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
h5iofrom 0.1.0 before 0.2.6

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat rates this vulnerability as Important severity because an attacker can achieve arbitrary execution within the process context without prior privileges, although exploitation requires local interaction to load malicious data. The affected library is not part of default system installations and is typically utilized within standalone data-processing environments rather than persistently exposed daemons. As a result, the risk is confined to individual workloads or user accounts that ingest datasets originating from unverified external sources.

Red Hat's mitigation

Do not load or process HDF5 files from untrusted or unverified external sources.

If processing untrusted datasets is required, execute workloads within an isolated container or restricted sandbox running under an unprivileged user account with minimal access to local storage and network resources.

Caveat: Sandboxing or container isolation mitigates lateral movement and host compromise but does not prevent malicious code execution within the isolated container boundary itself.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-120499.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON