CVE-2026-34181

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.4; sources differ by 0.0.

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

A fix is available — apply it.

Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery.

Impact Summary: An attacker impersonating a user can cause a service reading PKCS#12 files to accept forged certificates and private keys with a 1 in 256 probability.

If a service accepting PKCS#12 files is using passwords for authenticating the received files, the attacker can create unencrypted PKCS#12 files that use PBMAC1 authentication that specifies an HMAC key of only one byte, allowing them to craft a file that will be accepted with a 1 in 256 probability. That would then cause the service to accept a certificate and private key controlled by the attacker.

The FIPS modules are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

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

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (5)

Auto-updated Jun 12, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic
https://openssl-library.org/news/secadv/20260609.txt
github_commit

commit ec36f2417c4d (openssl/openssl)

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

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

commit 85dcbb3abaa4 (openssl/openssl)

Fix landed in openssl/openssl commit 85dcbb3abaa4 — awaiting tagged release

https://github.com/openssl/openssl/commit/85dcbb3abaa4878af5c8fbbe11bce708fcf984a7
github_commit

commit 79eb76a937e4 (openssl/openssl)

Fix landed in openssl/openssl commit 79eb76a937e4 — awaiting tagged release

https://github.com/openssl/openssl/commit/79eb76a937e474bb7610a0a3dc57131dc8dc6610
github_commit

commit 0300eb9ddce7 (openssl/openssl)

Fix landed in openssl/openssl commit 0300eb9ddce7 — awaiting tagged release

https://github.com/openssl/openssl/commit/0300eb9ddce7a0895bf301a4b0c03a9da2313a0f

Vendor Advisories for CVE-2026-34181(7)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.5-1ubuntu3.2) @ resolute2026-08-21ubuntu
redhatinsights-proxy/insights-proxy-container-rhel9:17828905032026-07-01redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatrhui5/rhua-rhel9:17815257392026-06-16redhat
redhatopenssl-1:3.5.5-4.el9_82026-06-11redhat
redhatopenssl-1:3.5.5-4.el10_22026-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

(5 across 5 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.7-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.7-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl—3.5.7-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.6-1~deb13u1 (11 versions)3.5.6-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.6.2-1 (19 versions)3.6.3-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 33× in last 7d / 147× 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 326 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-34181?
CVE-2026-34181 is a high vulnerability published on June 9, 2026. Issue Summary: The PKCS#12 file processing fails to perform sufficient input validation for files that use Password-Based Message Authentication Code 1 (PBMAC1) integrity mechanism allowing a certificate and private key forgery. Impact Summary: An attacker impersonating a user can cause a service…
When was CVE-2026-34181 disclosed?
CVE-2026-34181 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34181 actively exploited?
CVE-2026-34181 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 85.2% of all scored CVEs.
What is the CVSS score of CVE-2026-34181?
CVE-2026-34181 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-34181?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34181, 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-34181

Explore →

Is Your Infrastructure Affected by CVE-2026-34181?

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

Start Free Scan →Browse All CVEs