CVE-2026-45447

CRITICALPre-NVD 8.89.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.0%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.

Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.

When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.

In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.

Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.

The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

CVSS v3
8.8
EG Score
9.8CRITICALmedium confidence
EG Risk
46
EG Risk 46/100

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%
Exploitation4% × 40%
Automatability0% × 15%
EPSS PROB
4.0%
EPSS %ILE
90th
KEV
Not listed

Published

June 9, 2026

Last Modified

September 18, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available.
generic
https://openssl-library.org/news/secadv/20260609.txt

Vendor Advisories for CVE-2026-45447(20)

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

Patch Availability(21)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuopenssl (1.0.2g-1ubuntu4.20+esm16) @ xenial2026-09-18ubuntu
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.2) @ resolute2026-09-18ubuntu
redhatopenssl-0:1.0.1e-61.el6_10.12026-09-11redhat
redhatrhcos-412.86.202608241157-02026-09-03redhat
redhatopenssl-1:1.0.2k-26.el7_9.22026-08-24redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatmulticluster-engine/console-mce-rhel9:17850786042026-07-29redhat
redhatrhacm2/console-rhel9:17850785812026-07-29redhat
redhatcompat-openssl11-1:1.1.1k-5.el9_8.42026-07-23redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17835391562026-07-15redhat
redhatcompat-openssl11-1:1.1.1k-4.el9_2.22026-07-13redhat
redhatcompat-openssl11-1:1.1.1k-5.el9_4.32026-07-13redhat
redhatcompat-openssl10-1:1.0.2o-4.el8_10.32026-07-07redhat
redhatcompat-openssl10-1:1.0.2o-4.el8_8.12026-07-07redhat
redhatcompat-openssl11-1:1.1.1k-5.el9_6.32026-07-06redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatopenssl-1:1.1.1k-16.el8_62026-06-16redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatopenssl-1:3.5.5-4.el10_22026-06-11redhat
redhatopenssl-1:3.5.5-4.el9_82026-06-11redhat

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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.3.7-r1: fixed in 3.3.7-r1
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
openssl—
  • 1.0.2 up to 3.5.7-r0: fixed in 3.5.7-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
openssl1.1.1k-1 ... 1.1.1w-0~deb11u1 (23 versions)
  • every version up to 1.1.1w-0+deb11u8: fixed in 1.1.1w-0+deb11u8
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.0.10-1 ... 3.0.9-1 (22 versions)
  • every version up to 3.0.20-1~deb12u2: fixed in 3.0.20-1~deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.5.6-1~deb13u1 (11 versions)
  • every version up to 3.5.6-1~deb13u2: fixed in 3.5.6-1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
openssl3.5.1-1 ... 3.6.2-1 (22 versions)
  • every version up to 3.6.3-1: fixed in 3.6.3-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(12)

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 4× in last 7d / 39× 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 752 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45447?
CVE-2026-45447 is a critical vulnerability published on June 9, 2026. Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification. Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution. When processing a PKCS#7 or S/MIME signed…
When was CVE-2026-45447 disclosed?
CVE-2026-45447 was first published on June 9, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45447 actively exploited?
CVE-2026-45447 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.0% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45447?
CVE-2026-45447 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-45447?
A fix for CVE-2026-45447 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45447 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-45447

Explore →

Is Your Infrastructure Affected by CVE-2026-45447?

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

Book a Demo →Browse All CVEs