CVE-2026-63073

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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 — 4 sources updated 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.2%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 25, 2026

Last Modified

September 11, 2026

Advisory Details (5)

Auto-updated Oct 9, 2026
Patch available. 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(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.4) @ resolute2026-10-10ubuntu
redhatcert-manager/jetstack-cert-manager-rhel9:17905899122026-09-28redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17905899142026-09-28redhat
redhatcert-manager/cert-manager-operator-rhel9:17905898552026-09-28redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17902237192026-09-28redhat
redhatcert-manager/jetstack-cert-manager-rhel9:17902232792026-09-28redhat
redhatcert-manager/cert-manager-operator-rhel9:17902724262026-09-28redhat
redhatrhui5/rhua-rhel9:17902420042026-09-24redhat
redhatrhui5/installer-rhel9:17894829612026-09-16redhat
redhatopenssl-1:3.5.8-1.el9_82026-09-14redhat
redhatopenssl-1:3.5.8-1.el10_22026-09-14redhat
redhatopenssl3-main-3.5.8-0.1.hum12026-08-25redhat
redhatopenssl-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

(6 across 6 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.4.0 up to 3.3.7-r1: fixed in 3.3.7-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.4.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.4.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 3.4.0 up to 3.5.8-r0: fixed in 3.5.8-r0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.5.7-1~deb13u1 (13 versions)
  • every version up to 3.5.7-1~deb13u2: fixed in 3.5.7-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.6.3-1 (23 versions)
  • every version up to 3.6.4-1: fixed in 3.6.4-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 59× in last 7d / 326× 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 468 total refreshes for this CVE.

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

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 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.2% probability of exploitation in the next 30 days (66th percentile of EPSS-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?
A fix for CVE-2026-63073 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63073 are linked in the Vendor Advisories panel on this page.

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.