CVE-2026-75432

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreHIGH confidence

Score 5.1 from GitHub Security Advisory published 2026-09-22. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
5.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

An issue in yaml-cpp 0.9.0 allows a remote attacker to obtain sensitive information via the src/scanner.cpp, Scanner::PopIndent(), and Scanner::PushIndentTo() components

CVSS v3
5.1
EG Score
5.1MEDIUMhigh confidence
EG Risk
23
EG Risk 23/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity51% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 22, 2026

Last Modified

October 3, 2026

Advisory Details (2)

Auto-updated Oct 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

[Bug]Scanner indent-stack underflow: PopIndent/PushIndentTo dereference *m_indents.top() on an empty stack (wild read, deterministic crash / remote DoS) (CWE-822) · Issue #1475 · jbeder/yaml-cpp · GitHub

https://github.com/jbeder/yaml-cpp/issues/1475
github_pr

fix: fix stack underflow of PopIndent

Fix merged in jbeder/yaml-cpp PR #1476 on 2026-08-10 — awaiting tagged release

https://github.com/jbeder/yaml-cpp/pull/1476

Vendor Advisories for CVE-2026-75432(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
yaml-cpp0.7.0+dfsg-8 ... 0.9.0+dfsg-9 (19 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
yaml-cpp0.8.0+dfsg-7 ... 0.9.0+dfsg-9 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
yaml-cpp0.8.0+dfsg-7 ... 0.9.0+dfsg-9 (12 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 25× in last 30d)

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.

  1. 2026-10-04 23:22 UTCEPSS rescore
  2. 2026-10-04 18:47 UTCEG score recompute
  3. 2026-10-04 18:47 UTCGHSA enrichment
  4. 2026-10-03 16:23 UTCGHSA enrichment
  5. 2026-10-03 16:10 UTCEG score recompute▲ 5.10
  6. 2026-10-03 16:09 UTCGHSA enrichment
  7. 2026-10-03 16:09 UTCMITRE cvelistV5CVSS v3 → 5.1 · severity → MEDIUM
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 05:03 UTCGHSA enrichment
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 10:38 UTCEG score recompute
  12. 2026-09-30 10:38 UTCGHSA enrichment
  13. 2026-09-29 15:24 UTCEPSS rescore
  14. 2026-09-28 13:52 UTCEPSS rescore
  15. 2026-09-27 16:01 UTCGHSA enrichment
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-26 00:28 UTCEPSS rescore
  19. 2026-09-24 21:37 UTCEG score recompute
  20. 2026-09-24 21:37 UTCGHSA enrichment
  21. 2026-09-24 14:04 UTCEPSS rescore
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-22 20:32 UTCNVD update
  24. 2026-09-22 19:48 UTCEG score recompute
  25. 2026-09-22 19:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-75432?
CVE-2026-75432 is a medium vulnerability published on September 22, 2026. An issue in yaml-cpp 0.9.0 allows a remote attacker to obtain sensitive information via the src/scanner.cpp, Scanner::PopIndent(), and Scanner::PushIndentTo() components
When was CVE-2026-75432 disclosed?
CVE-2026-75432 was first published on September 22, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-75432 actively exploited?
CVE-2026-75432 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-75432?
CVE-2026-75432 has a CVSS v3.1 base score of 5.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-75432?
An upstream fix for CVE-2026-75432 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-75432 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-75432

Explore →

Is Your Infrastructure Affected by CVE-2026-75432?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs