CVE-2026-2100

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.2%, top 35% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in p11-kit. A remote attacker could exploit this vulnerability by calling the C_DeriveKey function on a remote token with specific IBM kyber or IBM btc derive mechanism parameters set to NULL. This could lead to the RPC-client attempting to return an uninitialized value, potentially resulting in a NULL dereference or undefined behavior. This issue may cause an application level denial of service or other unpredictable system states.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
65%
KEV
Not listed

Published

March 26, 2026

Last Modified

August 25, 2026

Advisory Details (9)

Auto-updated Jun 22, 2026
Patch available. Sources: redhat, github_pr.
github_pr Patch Available

Fix issues found by static analysis

Patch available: p11-glue/p11-kit 0.26.2 (PR #740 merged 2026-01-27)

https://github.com/p11-glue/p11-kit/pull/740
redhat Patch Available

2437308 – (CVE-2026-2100) CVE-2026-2100 p11-kit: NULL dereference via C_DeriveKey with specific NULL parameters

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2437308
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-2100
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:18599
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:18143

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17809462392026-06-22redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17804204282026-06-02redhat
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatp11-kit-0:0.26.2-1.el102026-05-19redhat
redhatp11-kit-0:0.26.2-1.el92026-05-19redhat
redhatp11-kit-main-0.26.2-1.1.hum12026-04-08redhat

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.21(1)
PackageVulnerable rangeFixed inDependents
p11-kit0.26.2-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
p11-kit0.26.2-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
p11-kit0.26.2-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
p11-kit0.26.2-r0
Debian:14(1)
PackageVulnerable rangeFixed inDependents
p11-kit0.25.10-1, 0.25.5-3, 0.25.9-1, 0.25.9-2, 0.26.2-10.26.2-2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 30× in last 7d / 110× 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 250 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-2100?
CVE-2026-2100 is a high vulnerability published on March 26, 2026. A flaw was found in p11-kit. A remote attacker could exploit this vulnerability by calling the C_DeriveKey function on a remote token with specific IBM kyber or IBM btc derive mechanism parameters set to NULL. This could lead to the RPC-client attempting to return an uninitialized value,…
When was CVE-2026-2100 disclosed?
CVE-2026-2100 was first published in the National Vulnerability Database on March 26, 2026, with the most recent update on August 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2100 actively exploited?
CVE-2026-2100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 35.3% of all scored CVEs.
What is the CVSS score of CVE-2026-2100?
CVE-2026-2100 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-2100?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2100, 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-2100

Explore →

Is Your Infrastructure Affected by CVE-2026-2100?

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