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% (65th percentile of EPSS-scored CVEs). GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
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.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 26, 2026

Last Modified

September 29, 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
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-2100
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:7065
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:27998
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:22634
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:21275
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:18599
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

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

Vendor Advisories for CVE-2026-2100(10)

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

Patch Availability(7)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
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 rangeFix by version rangeDependents
p11-kit—
  • every version up to 0.26.2-r0: fixed in 0.26.2-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
p11-kit—
  • every version up to 0.26.2-r0: fixed in 0.26.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
p11-kit—
  • every version up to 0.26.2-r0: fixed in 0.26.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
p11-kit—
  • every version up to 0.26.2-r0: fixed in 0.26.2-r0
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
p11-kit0.25.10-1, 0.25.5-3, 0.25.9-1, 0.25.9-2, 0.26.2-1
  • every version up to 0.26.2-2: fixed in 0.26.2-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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 302 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 on March 26, 2026, with the most recent update on September 29, 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.2% probability of exploitation in the next 30 days (66th percentile of EPSS-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?
A fix for CVE-2026-2100 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2100 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs