CVE-2026-63385

CRITICALPre-NVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — Patch released this week
9.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.2Exploit: None knownExposed: 0

A fix is available — apply it.

Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, libevent has two HTTP parsing weaknesses in http.c. evhttp_decode_uri_internal decodes percent-encoded %00 bytes into literal NUL characters, which can cause downstream C string operations to truncate a path and bypass validation performed on a different representation. evhttp_header_is_valid_value also accepts obsolete line folding in header values containing carriage return or line feed characters, allowing a proxy and libevent to interpret headers differently and enabling header injection or access control bypass. The CRLF header acceptance is fixed in versions 2.1.13 and 2.2.2-alpha, but the reviewed patches do not clearly remediate the URI NUL-truncation condition.

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

Published

August 20, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

HTTP header handling bugs create risk of access control bypass. · Advisory · libevent/libevent · GitHub

https://github.com/libevent/libevent/security/advisories/GHSA-jcwh-pvf2-73p2
github_release Patch Available

Libevent 2.2.2-alpha

Patch available: libevent/libevent release-2.2.2-alpha

https://github.com/libevent/libevent/releases/tag/release-2.2.2-alpha
github_release Patch Available

Libevent 2.1.13-stable

Patch available: libevent/libevent release-2.1.13-stable

https://github.com/libevent/libevent/releases/tag/release-2.1.13-stable
github_commit Patch Available

commit 9170dd35e647 (libevent/libevent)

Patch available: libevent/libevent release-2.1.13-stable (contains commit 9170dd35e647)

https://github.com/libevent/libevent/commit/9170dd35e64714613e8d13b290587cfc28e258e2
github_commit Patch Available

commit 758be0c0f69c (libevent/libevent)

Patch available: libevent/libevent release-2.2.2-alpha (contains commit 758be0c0f69c)

https://github.com/libevent/libevent/commit/758be0c0f69c1934ef9a84ab39e9f9e5fde2e6d0

Vendor Advisories for CVE-2026-63385(1)

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
ubuntulibevent-pthreads-2.1-7t64 (2.1.12-stable-10ubuntu0.1) @ resolute2026-09-19ubuntu
redhatlibevent-0:2.1.13-1.el10_22026-09-16redhat
redhatlibevent-0:2.1.8-11.el8_102026-09-16redhat
redhatlibevent-0:2.1.13-1.el9_82026-09-16redhat
redhatlibevent-main-2.1.13-0.1.hum12026-09-03redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libevent2.1.12-stable-10 ... 2.1.13-stable-1 (7 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libevent2.1.12-stable-10, 2.1.13-stable-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libevent2.1.12-stable-102.1.13-stable-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 52× in last 7d / 143× 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 143 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63385?
CVE-2026-63385 is a critical vulnerability published on August 20, 2026. Libevent is an event notification library. Prior to 2.1.13 and 2.2.2-alpha, libevent has two HTTP parsing weaknesses in http.c. evhttpdecodeuriinternal decodes percent-encoded %00 bytes into literal NUL characters, which can cause downstream C string operations to truncate a path and bypass…
When was CVE-2026-63385 disclosed?
CVE-2026-63385 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63385 actively exploited?
CVE-2026-63385 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 65.6% of all scored CVEs.
What is the CVSS score of CVE-2026-63385?
CVE-2026-63385 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-63385?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63385, 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-63385

Explore →

Is Your Infrastructure Affected by CVE-2026-63385?

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

Start Free Scan →Browse All CVEs