libfyaml 0.9.6 contains a stack exhaustion vulnerability in fy_atom_iter_format(). When processing a specially crafted YAML document containing a very large literal or folded block scalar, the function repeatedly grows an internal buffer using alloca() inside a loop. The allocated stack memory is not released until the function returns, causing cumulative stack growth that can exceed the process stack limit and result in SIGSEGV and denial of service.
CVE-2026-88359
Score 6.5 from GitHub Security Advisory published 2026-09-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.
- Lower severity and no public exploit yet
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 6.5
- EG Score
- 6.5MEDIUMhigh confidence
- EG Risk
- 45EG Risk 45/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 computedSeverity65% × 45%Exploitation40% × 40%Automatability0% × 15%CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).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
- 14th
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).
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 public PoC (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 24, 2026
Last Modified
September 25, 2026
Advisory Details (3)
Auto-updated Sep 25, 2026commit 20502068902d (pantoniou/libfyaml)
Fix landed in pantoniou/libfyaml commit 20502068902d — awaiting tagged release
https://github.com/pantoniou/libfyaml/commit/20502068902d58c076da873117985798df2c7e74commit 93741a7c9331 (pantoniou/libfyaml)
Fix landed in pantoniou/libfyaml commit 93741a7c9331 — awaiting tagged release
https://github.com/pantoniou/libfyaml/commit/93741a7c9331da9da65ef7a25f2d7d6a817a1c29[Bug]Stack exhaustion (SIGSEGV) in fy_atom_iter_format() via alloca() growth loop when parsing huge literal/folded block scalars(CWE-770 / CWE-121) · Issue #315 · pantoniou/libfyaml · GitHub
https://github.com/pantoniou/libfyaml/issues/315Vendor Advisories for CVE-2026-88359(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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libfyaml | 0.7.12-2 ... 0.9.4-1 (7 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libfyaml | 0.8-1 ... 0.9.4-1 (6 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libfyaml | 0.8-1 ... 0.9.4-1 (6 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 32× 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.
- 2026-10-04 23:22 UTCEPSS rescore
- 2026-10-04 20:54 UTCGHSA enrichment
- 2026-10-03 20:34 UTCEG score recompute
- 2026-10-03 20:34 UTCGHSA enrichment
- 2026-10-02 20:14 UTCEG score recompute
- 2026-10-02 20:14 UTCGHSA enrichment
- 2026-10-01 19:53 UTCEG score recompute
- 2026-10-01 19:53 UTCGHSA enrichment
- 2026-10-01 19:51 UTCEPSS rescore
- 2026-09-30 19:33 UTCEG score recompute
- 2026-09-30 19:33 UTCGHSA enrichment
- 2026-09-30 15:04 UTCEPSS rescore
- 2026-09-29 19:13 UTCEG score recompute
- 2026-09-29 19:13 UTCGHSA enrichment
- 2026-09-28 18:43 UTCEG score recompute
- 2026-09-28 18:43 UTCGHSA enrichment
- 2026-09-28 13:52 UTCEPSS rescore
- 2026-09-27 18:24 UTCEG score recompute
- 2026-09-27 18:24 UTCGHSA enrichment
- 2026-09-27 13:48 UTCEPSS rescore
- 2026-09-26 18:04 UTCEG score recompute
- 2026-09-26 18:04 UTCGHSA enrichment
- 2026-09-26 15:59 UTCEPSS rescore
- 2026-09-25 17:44 UTCEG score recompute
- 2026-09-25 17:44 UTCGHSA enrichment
Show 7 moreShow fewer
- 2026-09-25 16:24 UTCEG score recompute▲ 6.50
- 2026-09-25 16:24 UTCGHSA enrichment
- 2026-09-25 16:24 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
- 2026-09-24 21:16 UTCGHSA enrichment
- 2026-09-24 14:32 UTCNVD update
- 2026-09-24 14:17 UTCEG score recompute
- 2026-09-24 14:16 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-88359?
When was CVE-2026-88359 disclosed?
Is CVE-2026-88359 actively exploited?
What is the CVSS score of CVE-2026-88359?
How do I remediate CVE-2026-88359?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-88359
Is Your Infrastructure Affected by CVE-2026-88359?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.