CVE-2026-11979

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: LOW) published 2026-06-29. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.

This issue has been fixed in the commit c2e233fc.

NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.

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

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 30, 2026
No patch confirmed yet.
generic

Client Challenge

https://gitlab.gnome.org/GNOME/libxml2/-/commit/c2e233fc1b341685fc99621b2768b503f777a72e
generic

Vulnerability in libxml2 software | CERT Polska

https://cert.pl/en/posts/2026/06/CVE-2026-11979

Vendor Advisories for CVE-2026-11979(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlibxml2-0:2.9.7-21.el8_10.72026-08-31redhat
redhatlibxml2-0:2.9.13-14.el9_8.42026-08-31redhat
redhatdiscovery/discovery-server-rhel9:17882057792026-08-31redhat
redhatlibxml2-0:2.12.5-10.el10_2.32026-08-27redhat
redhatlibxml2-main-2.15.3-0.1.1.hum12026-06-30redhat

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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.3+dfsg-0exp1 ... 2.9.14+dfsg-1.3~deb12u6 (68 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.3+dfsg-0exp1 ... 2.9.14+dfsg-1.3~deb12u6 (48 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.3+dfsg-1 (30 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libxml22.12.7+dfsg+really2.9.14-2.1 ... 2.15.3+dfsg-1 (27 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 86× 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.

Showing the most recent 100 of 274 total refreshes for this CVE.

  1. 2026-09-11 14:52 UTCEPSS rescore
  2. 2026-09-11 09:36 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-06 14:44 UTCEG score recompute
  7. 2026-09-06 14:44 UTCVendor advisory
  8. 2026-09-06 14:44 UTCGHSA enrichment
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 18:45 UTCEG score recompute
  16. 2026-08-30 18:45 UTCVendor advisory
  17. 2026-08-30 18:45 UTCGHSA enrichment
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-27 22:48 UTCEG score recompute
  21. 2026-08-27 22:48 UTCVendor advisory
  22. 2026-08-27 22:48 UTCGHSA enrichment
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-25 01:09 UTCEG score recompute
Show 75 more
  1. 2026-08-25 01:09 UTCVendor advisory
  2. 2026-08-25 01:09 UTCGHSA enrichment
  3. 2026-08-24 12:41 UTCEG score recompute
  4. 2026-08-24 12:41 UTCVendor advisory
  5. 2026-08-24 12:41 UTCGHSA enrichment
  6. 2026-08-23 23:09 UTCVendor advisory
  7. 2026-08-23 23:09 UTCGHSA enrichment
  8. 2026-08-23 10:26 UTCEG score recompute
  9. 2026-08-23 10:26 UTCVendor advisory
  10. 2026-08-23 10:26 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 21:47 UTCVendor advisory
  13. 2026-08-22 21:47 UTCGHSA enrichment
  14. 2026-08-22 08:58 UTCEG score recompute
  15. 2026-08-22 08:58 UTCVendor advisory
  16. 2026-08-22 08:58 UTCGHSA enrichment
  17. 2026-08-21 23:48 UTCEPSS rescore
  18. 2026-08-21 19:17 UTCVendor advisory
  19. 2026-08-21 19:17 UTCGHSA enrichment
  20. 2026-08-21 06:49 UTCEG score recompute
  21. 2026-08-21 06:49 UTCVendor advisory
  22. 2026-08-21 06:48 UTCGHSA enrichment
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 18:19 UTCVendor advisory
  25. 2026-08-20 18:19 UTCGHSA enrichment
  26. 2026-08-20 05:49 UTCEG score recompute
  27. 2026-08-20 05:49 UTCVendor advisory
  28. 2026-08-20 05:49 UTCGHSA enrichment
  29. 2026-08-19 17:03 UTCEPSS rescore
  30. 2026-08-19 12:36 UTCVendor advisory
  31. 2026-08-19 12:36 UTCGHSA enrichment
  32. 2026-08-18 23:11 UTCEG score recompute
  33. 2026-08-18 23:11 UTCVendor advisory
  34. 2026-08-18 23:11 UTCGHSA enrichment
  35. 2026-08-18 13:48 UTCEPSS rescore
  36. 2026-08-17 08:27 UTCVendor advisory
  37. 2026-08-17 08:27 UTCGHSA enrichment
  38. 2026-08-16 19:59 UTCEG score recompute
  39. 2026-08-16 19:59 UTCVendor advisory
  40. 2026-08-16 19:59 UTCGHSA enrichment
  41. 2026-08-16 14:56 UTCEPSS rescore
  42. 2026-08-16 06:23 UTCEG score recompute
  43. 2026-08-16 06:23 UTCVendor advisory
  44. 2026-08-16 06:23 UTCGHSA enrichment
  45. 2026-08-16 02:14 UTCEPSS rescore
  46. 2026-08-15 17:56 UTCVendor advisory
  47. 2026-08-15 17:56 UTCGHSA enrichment
  48. 2026-08-15 05:28 UTCEG score recompute
  49. 2026-08-15 05:28 UTCVendor advisory
  50. 2026-08-15 05:28 UTCGHSA enrichment
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 16:56 UTCVendor advisory
  53. 2026-08-14 16:56 UTCGHSA enrichment
  54. 2026-08-14 04:19 UTCEG score recompute
  55. 2026-08-14 04:19 UTCVendor advisory
  56. 2026-08-14 04:19 UTCGHSA enrichment
  57. 2026-08-13 22:00 UTCEPSS rescore
  58. 2026-08-13 15:51 UTCVendor advisory
  59. 2026-08-13 15:51 UTCGHSA enrichment
  60. 2026-08-13 03:09 UTCVendor advisory
  61. 2026-08-13 03:09 UTCGHSA enrichment
  62. 2026-08-12 14:41 UTCEG score recompute
  63. 2026-08-12 14:41 UTCVendor advisory
  64. 2026-08-12 14:41 UTCGHSA enrichment
  65. 2026-08-12 13:50 UTCEPSS rescore
  66. 2026-08-12 02:13 UTCVendor advisory
  67. 2026-08-12 02:13 UTCGHSA enrichment
  68. 2026-08-11 13:45 UTCEG score recompute
  69. 2026-08-11 13:45 UTCVendor advisory
  70. 2026-08-11 13:45 UTCGHSA enrichment
  71. 2026-08-11 13:42 UTCEPSS rescore
  72. 2026-08-11 01:17 UTCEG score recompute
  73. 2026-08-11 01:17 UTCVendor advisory
  74. 2026-08-11 01:16 UTCGHSA enrichment
  75. 2026-08-10 23:59 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11979?
CVE-2026-11979 is a high vulnerability published on June 29, 2026. libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow…
When was CVE-2026-11979 disclosed?
CVE-2026-11979 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11979 actively exploited?
CVE-2026-11979 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 95.6% of all scored CVEs.
What is the CVSS score of CVE-2026-11979?
CVE-2026-11979 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-11979?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11979, 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-11979

Explore →

Is Your Infrastructure Affected by CVE-2026-11979?

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

Start Free Scan →Browse All CVEs