YAML-LibYAML prior to 0.903.0 for Perl uses 2-args open, allowing existing files to be modified
Loading...
Loading...
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-06-01. NVD baseline CVSS 9.1; sources differ by 0.0.
YAML-LibYAML prior to 0.903.0 for Perl uses 2-args open, allowing existing files to be modified
June 1, 2025
July 2, 2025
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libyaml-libyaml-perl (0.89+ds-1ubuntu0.24.04.1) @ noble | 2026-05-30 | ubuntu |
| redhat | perl-YAML-LibYAML-1:0.82-6.el9_4.1 | 2025-06-23 | redhat |
| redhat | perl-YAML-LibYAML-1:0.70-2.el8_10 | 2025-06-23 | redhat |
| redhat | perl-YAML-LibYAML-1:0.82-6.1.el9_6 | 2025-06-23 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Explore the affected products and dependency analysis for CVE-2025-40908
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.