CVE-2026-32777

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

libexpat before 2.7.5 allows an infinite loop while parsing DTD content.

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

Published

March 16, 2026

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jul 14, 2026
⚠️ Active exploitation confirmed. Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic🔴 Active Exploitation

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
generic

OSS Fuzz

https://issues.oss-fuzz.com/issues/486993411
github_pr

[CVE-2026-32777] lib: Reject `XML_TOK_INSTANCE_START` infinite loop in `entityValueProcessor` (fixes #1161)

Fix merged in libexpat/libexpat PR #1162 on 2026-03-16 — awaiting tagged release

https://github.com/libexpat/libexpat/pull/1162
github_pr

Prepare release 2.7.5 (part of #1157, ETA 2026-03-17)

Fix merged in libexpat/libexpat PR #1159 on 2026-03-17 — awaiting tagged release

https://github.com/libexpat/libexpat/pull/1159
generic

[CVE-REQUESTED] OSS-Fuzz/ClusterFuzz finding 486993411 · Issue #1161 · libexpat/libexpat · GitHub

https://github.com/libexpat/libexpat/issues/1161

Vendor Advisories for CVE-2026-32777(2)

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

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
expat—2.7.5-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
expat—2.7.5-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
expat—2.7.5-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
expat—2.7.5-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
expat—2.7.5-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
expat2.2.10-2 ... 2.8.2-1~deb13u1 (47 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
expat2.5.0-1 ... 2.8.2-1~deb13u1 (25 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
expat2.7.1-2 ... 2.8.1-1 (9 versions)2.8.2-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
expat2.7.1-2, 2.7.2-1, 2.7.3-1, 2.7.3-2, 2.7.4-12.7.5-1—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32777?
CVE-2026-32777 is a medium vulnerability published on March 16, 2026. libexpat before 2.7.5 allows an infinite loop while parsing DTD content.
When was CVE-2026-32777 disclosed?
CVE-2026-32777 was first published in the National Vulnerability Database on March 16, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32777 actively exploited?
CVE-2026-32777 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 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-32777?
CVE-2026-32777 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-32777?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32777, 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-32777

Explore →

Is Your Infrastructure Affected by CVE-2026-32777?

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

Start Free Scan →Browse All CVEs