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 36% 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 — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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
63.8%
KEV
Not listed

Published

March 26, 2026

Last Modified

July 19, 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
https://access.redhat.com/errata/RHSA-2026:7065
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:27998
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22634
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:21275
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

Vendor Advisories for CVE-2026-2100(8)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 52× 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 131 total refreshes for this CVE.

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

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 July 19, 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 63.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

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

Start Free Scan →Browse All CVEs