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.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.4Exploit: NoneExposed: 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
9.6%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 15, 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-07-16ubuntu
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.

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 10× in last 7d / 115× 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 181 total refreshes for this CVE.

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

Explore the affected products and dependency analysis for 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