CVE-2026-63073

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to ERR_raise_data().

Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender.

CWE: CWE-134 (Use of Externally-Controlled Format String)

Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as "CN=%s%n" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses.

Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution.

FIPS impact: no

No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
59%
KEV
Not listed

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (5)

Auto-updated Sep 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit a7e5a6eea8fd (openssl/openssl)

Fix landed in openssl/openssl commit a7e5a6eea8fd — awaiting tagged release

https://github.com/openssl/openssl/commit/a7e5a6eea8fd3ccca6b6fbba031a5fbf8a3d93b4
github_commit

commit 7eb2e3ec9d1d (openssl/openssl)

Fix landed in openssl/openssl commit 7eb2e3ec9d1d — awaiting tagged release

https://github.com/openssl/openssl/commit/7eb2e3ec9d1d4f35c8022fccd4b03398b3f33e21
github_commit

commit 6a0acc072b4d (openssl/openssl)

Fix landed in openssl/openssl commit 6a0acc072b4d — awaiting tagged release

https://github.com/openssl/openssl/commit/6a0acc072b4d37a7cac1252a29c1ce1f00c5ec29
github_commit

commit 0cc20b322639 (openssl/openssl)

Fix landed in openssl/openssl commit 0cc20b322639 — awaiting tagged release

https://github.com/openssl/openssl/commit/0cc20b322639919aa423e90799d9a57c3b4b76ca

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-09-19ubuntu
redhatopenssl-1:3.5.8-1.el10_22026-09-14redhat
redhatopenssl-1:3.5.8-1.el9_82026-09-14redhat
redhatopenssl-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat

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

(5 across 5 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.8-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.8-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.8-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)3.5.7-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 4.0.2-1 (28 versions)

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 88× in last 7d / 252× 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 252 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-63073?
CVE-2026-63073 is a critical vulnerability published on August 25, 2026. Issue summary: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to ERRraisedata(). Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate…
When was CVE-2026-63073 disclosed?
CVE-2026-63073 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63073 actively exploited?
CVE-2026-63073 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 41.0% of all scored CVEs.
What is the CVSS score of CVE-2026-63073?
CVE-2026-63073 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-63073?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63073, 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-63073

Explore →

Is Your Infrastructure Affected by CVE-2026-63073?

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