CVE-2026-71219

MEDIUMPre-NVD 4.74.7—
EchelonGraph scoreHIGH confidence

Score 4.7 from GitHub Security Advisory published 2026-09-03. a secondary CVSS source baseline 4.7; sources differ by 0.0.

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

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

A stack overflow vulnerability was found in gfs2-utils. The hash table traversal code in metawalk.c uses alloca() with an exponentially-derived size from the untrusted on-disk di_depth field without bounds validation. A crafted GFS2 filesystem image with a large di_depth value causes stack exhaustion and a denial of service when processed by fsck.gfs2, gfs2_edit, or savemeta.

CVSS v3
4.7
EG Score
4.7(high)
EG Risk
21(Track)
EG Risk 21/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
Severity47% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 4, 2026

Advisory Details (1)

Auto-updated Sep 3, 2026
No patch confirmed yet. Sources: redhat.
redhat

2507750 – (CVE-2026-71219) CVE-2026-71219 gfs2-utils: gfs2-utils: stack overflow via alloca(1<<di_depth) in hash table traversal

https://bugzilla.redhat.com/show_bug.cgi?id=2507750

Vendor Advisories for CVE-2026-71219(2)

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 rangeFixed inDependents
gfs2-utils3.5.0-2, 3.5.1-1, 3.5.1-2, 3.6.0-1, 3.6.1-1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
gfs2-utils3.6.1-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
gfs2-utils3.6.1-1——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 54× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 04:27 UTCEG score recompute
  3. 2026-09-20 04:27 UTCVendor advisory
  4. 2026-09-20 04:27 UTCGHSA enrichment
  5. 2026-09-19 02:16 UTCEG score recompute
  6. 2026-09-19 02:16 UTCVendor advisory
  7. 2026-09-19 02:15 UTCGHSA enrichment
  8. 2026-09-18 19:28 UTCEPSS rescore
  9. 2026-09-17 23:57 UTCEG score recompute
  10. 2026-09-17 23:57 UTCVendor advisory
  11. 2026-09-17 23:57 UTCGHSA enrichment
  12. 2026-09-16 21:20 UTCEG score recompute
  13. 2026-09-16 21:20 UTCVendor advisory
  14. 2026-09-16 21:20 UTCGHSA enrichment
  15. 2026-09-16 14:08 UTCEPSS rescore
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 18:20 UTCEG score recompute
  18. 2026-09-15 18:20 UTCVendor advisory
  19. 2026-09-15 18:20 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-14 15:29 UTCEG score recompute
  22. 2026-09-14 15:29 UTCVendor advisory
  23. 2026-09-14 15:29 UTCGHSA enrichment
  24. 2026-09-13 13:18 UTCEG score recompute
  25. 2026-09-13 13:18 UTCVendor advisory
Show 29 more
  1. 2026-09-13 13:18 UTCGHSA enrichment
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-12 11:06 UTCEG score recompute
  4. 2026-09-12 11:06 UTCVendor advisory
  5. 2026-09-12 11:06 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 08:36 UTCEG score recompute
  8. 2026-09-11 08:36 UTCGHSA enrichment
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-10 06:24 UTCGHSA enrichment
  11. 2026-09-09 04:12 UTCEG score recompute
  12. 2026-09-09 04:12 UTCGHSA enrichment
  13. 2026-09-08 22:01 UTCEPSS rescore
  14. 2026-09-08 01:57 UTCEG score recompute
  15. 2026-09-08 01:56 UTCGHSA enrichment
  16. 2026-09-06 23:45 UTCEG score recompute
  17. 2026-09-06 23:45 UTCGHSA enrichment
  18. 2026-09-06 13:48 UTCEPSS rescore
  19. 2026-09-05 21:33 UTCEG score recompute
  20. 2026-09-05 21:33 UTCGHSA enrichment
  21. 2026-09-04 19:22 UTCEG score recompute
  22. 2026-09-04 19:22 UTCGHSA enrichment
  23. 2026-09-04 18:49 UTCEG score recompute
  24. 2026-09-04 18:49 UTCGHSA enrichment
  25. 2026-09-03 18:18 UTCEG score recompute
  26. 2026-09-03 18:18 UTCGHSA enrichment
  27. 2026-09-03 13:14 UTCEG score recompute
  28. 2026-09-03 12:47 UTCEG score recompute
  29. 2026-09-03 12:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71219?
CVE-2026-71219 is a medium vulnerability published on September 3, 2026. A stack overflow vulnerability was found in gfs2-utils. The hash table traversal code in metawalk.c uses alloca() with an exponentially-derived size from the untrusted on-disk didepth field without bounds validation. A crafted GFS2 filesystem image with a large didepth value causes stack exhaustion…
When was CVE-2026-71219 disclosed?
CVE-2026-71219 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71219 actively exploited?
CVE-2026-71219 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-71219?
CVE-2026-71219 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-71219?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71219, 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-71219

Explore →

Is Your Infrastructure Affected by CVE-2026-71219?

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

Start Free Scan →Browse All CVEs