CVE-2025-11187

MEDIUMNVD 6.16.1
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-01-27. NVD baseline CVSS 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 6.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification.

Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of Service for an application that parses untrusted PKCS#12 files. The buffer overflow may also potentially enable code execution depending on platform mitigations.

When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2 salt and keylength parameters from the file are used without validation. If the value of keylength exceeds the size of the fixed stack buffer used for the derived key (64 bytes), the key derivation will overflow the buffer. The overflow length is attacker-controlled. Also, if the salt parameter is not an OCTET STRING type this can lead to invalid or NULL pointer dereference.

Exploiting this issue requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For this reason the issue was assessed as Moderate severity.

The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as PKCS#12 processing is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.

OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do not support PBMAC1 in PKCS#12.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
43(Track*)
EG Risk 43/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
Severity61% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
5%
EPSS %ILE
91%
KEV
Not listed

Published

January 27, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 7, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

GitHub - metadust/CVE-2025-11187: Stack buffer overflow in PKCS#12 PBMAC1 PBKDF2 keylength (OpenSSL 3.X) · GitHub

https://github.com/metadust/CVE-2025-11187
github_commit

commit e1079bc17ed9 (openssl/openssl)

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

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

commit 8caf359d6e46 (openssl/openssl)

Fix landed in openssl/openssl commit 8caf359d6e46 — awaiting tagged release

https://github.com/openssl/openssl/commit/8caf359d6e46fb413e8f5f0df765d2e8a51df4e8
github_commit

commit 205e3a55e16e (openssl/openssl)

Fix landed in openssl/openssl commit 205e3a55e16e — awaiting tagged release

https://github.com/openssl/openssl/commit/205e3a55e16e4bd08c12fdbd3416ab829c0f6206

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl-provider-legacy (3.5.3-1ubuntu3) @ questing2026-06-08ubuntu
redhatopenssl-main-3.5.6-0.1.hum12026-04-09redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17708363492026-02-24redhat
redhatrhui5/installer-rhel9:17706469252026-02-11redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17707404052026-02-10redhat
redhatdiscovery/discovery-ui-rhel9:17691117742026-02-02redhat
redhatopenssl-1:3.5.1-7.el10_12026-01-28redhat
redhatopenssl-1:3.2.2-16.el10_0.62026-01-28redhat
redhatopenssl-1:3.5.1-7.el9_72026-01-28redhat

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.5-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.5-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.5-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1, 3.5.1-1+deb13u1, 3.5.2-1, 3.5.3-1, 3.5.4-1~deb13u13.5.4-1~deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl3.5.1-1 ... 3.5.5-1~deb13u2 (8 versions)3.5.5-1

Weakness Classification(2)

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 9× in last 7d / 49× 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 150 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-11187?
CVE-2025-11187 is a medium vulnerability published on January 27, 2026. Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation which can trigger a stack-based buffer overflow, invalid pointer or NULL pointer dereference during MAC verification. Impact summary: The stack buffer overflow or NULL pointer dereference may cause a crash leading to Denial of…
When was CVE-2025-11187 disclosed?
CVE-2025-11187 was first published in the National Vulnerability Database on January 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-11187 actively exploited?
CVE-2025-11187 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 8.9% of all scored CVEs.
What is the CVSS score of CVE-2025-11187?
CVE-2025-11187 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2025-11187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-11187, 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-2025-11187

Explore →

Is Your Infrastructure Affected by CVE-2025-11187?

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