Security readout for executives and security teams
Plain-English summary
CVE-2026-2100 is a medium-severity p11-kit flaw that can make affected applications crash or behave unpredictably when handling certain remote cryptographic token requests. The business impact is availability, not data theft, based on the supplied CVSS vector.
Executive priority
Treat this as a routine but real availability risk. Patch affected Red Hat systems during the next normal maintenance window, faster for externally reachable token services or platforms supporting critical operations.
Technical view
p11-kit can mishandle NULL IBM kyber or IBM btc derive mechanism parameters in C_DeriveKey for a remote token. The RPC client may return an uninitialized value, leading to NULL dereference or undefined behavior. The listed weakness is CWE-824, with low availability impact only.
Likely exposure
Exposure is most likely on Red Hat Enterprise Linux 9 or 10 systems, listed Red Hat container images, RHUI 5, Insights proxy, Cost Management 4, and Hardened Images carrying affected p11-kit packages.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. The described scenario involves a remote attacker able to invoke affected p11-kit remote token behavior with specific NULL derive parameters, causing application-level denial of service or unpredictable states.
Researcher notes
The evidence supports denial of service and undefined behavior, not confidentiality or integrity compromise. Affected status is product-specific; RHEL 6, 7, 8, and OpenShift Container Platform 4 are listed as unaffected in the bundle.
Mitigation direction
- Apply the relevant Red Hat RHSA guidance for affected products.
- Track upstream p11-kit PR 740 and release 0.26.2 for vendor context.
- Prioritize internet-reachable or shared remote token services first.
- Review dependent containers and rebuilt images for affected p11-kit packages.
- If no advisory applies, check vendor support guidance before changing crypto components.
Validation and detection
- Inventory p11-kit versions across RHEL 9 and RHEL 10 hosts.
- Check affected Red Hat container images listed in the CVE record.
- Identify applications using p11-kit with remote PKCS#11 tokens.
- Review crash logs for p11-kit or PKCS#11 application failures.
- Confirm vendor advisory status after applying updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-824: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2100 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4redhatVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Made public.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:18143CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:18599CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:21275CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:22634CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:27998CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:7065CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-2100CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2437308CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/p11-glue/p11-kit/pull/740CVE reference, redhat
- https://github.com/p11-glue/p11-kit/releases/tag/0.26.2CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Access of Uninitialized Pointer
Access of Uninitialized Pointer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.