CVE-2026-56390

MEDIUMNVD 6.36.3
EchelonGraph scoreHIGH confidence

Score 6.3 from GitHub Security Advisory published 2026-07-29. NVD baseline CVSS 6.3; sources differ by 0.0.

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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GNU Bison improperly handles grammar‑defined output paths. Grammar directives such as %output and %header allow specifying file paths, which are accepted without restriction and override caller‑supplied output options. When processing attacker-supplied grammar, this behavior allows directing generated files to arbitrary writable locations on the filesystem, potentially overwriting existing files accessible to the Bison process.

Maintainers of this project were notified about this vulnerability, and fixed the issue in commit 8d101c19d4d9aaedf83a448c925513742d4efcf0. However, they did not provide vulnerable version range. Version 3.8.2 was tested and confirmed as vulnerable, other versions were not tested but might also be vulnerable.

CVSS v3
6.3
EG Score
6.3(high)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

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
Severity63% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 24, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

bison: tighten up output file names - bison.git - GNU bison (git mirror)

https://cgit.git.savannah.gnu.org/cgit/bison.git/commit/?id=8d101c19d4d9aaedf83a448c925513742d4efcf0
generic

Vulnerabilities in GNU Bison software | CERT Polska

https://cert.pl/en/posts/2026/07/CVE-2026-56389

Vendor Advisories for CVE-2026-56390(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
bison2:3.7.5+dfsg-1, 2:3.7.6+dfsg-1, 2:3.8.1+dfsg-1, 2:3.8.2+dfsg-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
bison2:3.8.2+dfsg-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
bison2:3.8.2+dfsg-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
bison2:3.8.2+dfsg-1

Weakness Classification(1)

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

All Vendor Advisories

(1)

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.

Data Freshness Timeline

(refreshed 24× in last 7d / 90× 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-08-25 18:33 UTCEG score recompute
  2. 2026-08-25 18:33 UTCVendor advisory
  3. 2026-08-25 18:33 UTCGHSA enrichment
  4. 2026-08-25 13:49 UTCEPSS rescore
  5. 2026-08-24 16:55 UTCEG score recompute 1.70
  6. 2026-08-24 16:55 UTCVendor advisory
  7. 2026-08-24 16:55 UTCGHSA enrichment
  8. 2026-08-24 16:15 UTCNVD updateCVSS v3 → 6.3
  9. 2026-08-24 05:33 UTCVendor advisory
  10. 2026-08-24 05:33 UTCGHSA enrichment
  11. 2026-08-23 03:59 UTCVendor advisory
  12. 2026-08-23 03:59 UTCGHSA enrichment
  13. 2026-08-22 02:26 UTCEG score recompute
  14. 2026-08-22 02:26 UTCVendor advisory
  15. 2026-08-22 02:26 UTCGHSA enrichment
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 00:52 UTCEG score recompute
  18. 2026-08-21 00:52 UTCVendor advisory
  19. 2026-08-21 00:52 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-19 23:19 UTCEG score recompute
  22. 2026-08-19 23:19 UTCVendor advisory
  23. 2026-08-19 23:19 UTCGHSA enrichment
  24. 2026-08-19 17:04 UTCEPSS rescore
  25. 2026-08-18 21:45 UTCEG score recompute
Show 65 more
  1. 2026-08-18 21:45 UTCVendor advisory
  2. 2026-08-18 21:45 UTCGHSA enrichment
  3. 2026-08-18 13:48 UTCEPSS rescore
  4. 2026-08-17 19:54 UTCEG score recompute
  5. 2026-08-17 19:54 UTCVendor advisory
  6. 2026-08-17 19:54 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 17:42 UTCEG score recompute
  9. 2026-08-16 17:42 UTCVendor advisory
  10. 2026-08-16 17:42 UTCGHSA enrichment
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 16:02 UTCEG score recompute
  14. 2026-08-15 16:02 UTCVendor advisory
  15. 2026-08-15 16:02 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 14:28 UTCEG score recompute
  18. 2026-08-14 14:28 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 12:55 UTCEG score recompute
  21. 2026-08-13 12:55 UTCGHSA enrichment
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-12 11:23 UTCGHSA enrichment
  24. 2026-08-11 09:49 UTCEG score recompute
  25. 2026-08-11 09:49 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 08:17 UTCEG score recompute
  28. 2026-08-10 08:17 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 06:44 UTCEG score recompute
  31. 2026-08-09 06:44 UTCGHSA enrichment
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 05:11 UTCEG score recompute
  34. 2026-08-08 05:11 UTCGHSA enrichment
  35. 2026-08-07 03:38 UTCEG score recompute
  36. 2026-08-07 03:38 UTCGHSA enrichment
  37. 2026-08-06 13:47 UTCEPSS rescore
  38. 2026-08-06 02:05 UTCEG score recompute
  39. 2026-08-06 02:05 UTCGHSA enrichment
  40. 2026-08-05 19:17 UTCEPSS rescore
  41. 2026-08-05 00:32 UTCEG score recompute
  42. 2026-08-05 00:32 UTCGHSA enrichment
  43. 2026-08-04 10:39 UTCEPSS rescore
  44. 2026-08-03 22:56 UTCEG score recompute
  45. 2026-08-03 22:56 UTCGHSA enrichment
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-02 21:24 UTCEG score recompute
  48. 2026-08-02 21:24 UTCGHSA enrichment
  49. 2026-08-02 02:27 UTCEPSS rescore
  50. 2026-08-01 19:51 UTCEG score recompute
  51. 2026-08-01 19:51 UTCGHSA enrichment
  52. 2026-08-01 04:16 UTCEPSS rescore
  53. 2026-07-31 18:18 UTCGHSA enrichment
  54. 2026-07-30 16:44 UTCEG score recompute
  55. 2026-07-30 16:44 UTCGHSA enrichment
  56. 2026-07-30 16:28 UTCEPSS rescore
  57. 2026-07-30 15:42 UTCEG score recompute
  58. 2026-07-30 15:42 UTCGHSA enrichment
  59. 2026-07-29 13:38 UTCEG score recompute
  60. 2026-07-29 13:38 UTCGHSA enrichment
  61. 2026-07-29 12:38 UTCEG score recompute
  62. 2026-07-29 12:38 UTCGHSA enrichment
  63. 2026-07-29 11:32 UTCEG score recompute
  64. 2026-07-29 10:23 UTCEG score recompute
  65. 2026-07-29 10:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56390?
CVE-2026-56390 is a medium vulnerability published on July 29, 2026. GNU Bison improperly handles grammar‑defined output paths. Grammar directives such as %output and %header allow specifying file paths, which are accepted without restriction and override caller‑supplied output options. When processing attacker-supplied grammar, this behavior allows directing…
When was CVE-2026-56390 disclosed?
CVE-2026-56390 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56390 actively exploited?
CVE-2026-56390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-56390?
CVE-2026-56390 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-56390?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56390, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56390?

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