# CVE-2026-2100: P11-kit: null dereference via c_derivekey with specific null parameters > A remote attacker can cause a denial of service in p11-kit by triggering a null dereference via specific C_DeriveKey parameters. - **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Mar 2026 - **Updated:** 14 Oct 2026 - **Also known as:** ALPINE-CVE-2026-2100, ALSA-2026:18143, ALSA-2026:18599, DEBIAN-CVE-2026-2100, ECHO-7889-82b6-071e, GHSA-hq85-3f6c-jx84, RHSA-2026:18143, RHSA-2026:18599, RHSA-2026:7065, RLSA-2026:18143, RLSA-2026:18599, openSUSE-SU-2026:10169-1 ## What is CVE-2026-2100? CVE-2026-2100 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-824 (Access of Uninitialized Pointer) ## Which versions are affected by CVE-2026-2100? It affects 7 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `p11-kit` | AlmaLinux:10 | All versions | 0.26.2-1.el10 | | `p11-kit-client` | AlmaLinux:10 | All versions | 0.26.2-1.el10 | | `p11-kit-devel` | AlmaLinux:10 | All versions | 0.26.2-1.el10 | | `p11-kit-server` | AlmaLinux:10 | All versions | 0.26.2-1.el10 | | `p11-kit-trust` | AlmaLinux:10 | All versions | 0.26.2-1.el10 | | `p11-kit` | AlmaLinux:9 | All versions | 0.26.2-1.el9 | | `p11-kit-client` | AlmaLinux:9 | All versions | 0.26.2-1.el9 | | `p11-kit-devel` | AlmaLinux:9 | All versions | 0.26.2-1.el9 | | `p11-kit-server` | AlmaLinux:9 | All versions | 0.26.2-1.el9 | | `p11-kit-trust` | AlmaLinux:9 | All versions | 0.26.2-1.el9 | | `p11-kit` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-client` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-client-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-server` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-server-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-trust` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-trust-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:0.26.2-1.el10 | | `p11-kit-client-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-server` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-server-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit-trust-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:0.26.2-1.el9 | | `p11-kit` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-client` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-client-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-server-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-trust` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `p11-kit-trust-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:0.26.2-1.el9 | | `mingw32-p11-kit` | Red Hat:hummingbird:1 | All versions | 0:0.26.2-1.1.hum1 | | `mingw64-p11-kit` | Red Hat:hummingbird:1 | All versions | 0:0.26.2-1.1.hum1 | | `p11-kit` | Red Hat:hummingbird:1 | All versions | 0:0.26.2-1.1.hum1 | | `p11-kit-client` | Red Hat:hummingbird:1 | All versions | 0:0.26.2-1.1.hum1 | | `p11-kit-devel` | Red Hat:hummingbird:1 | All versions | 0:0.26.2-1.1.hum1 | Products: P11-Kit Project P11-Kit, Redhat Cert-Manager Operator, Redhat Cost Management Metrics Operator, Redhat Enterprise Linux, Redhat Hardened Images, Redhat Insights-Proxy, Redhat Update Infrastructure. ## How do I fix CVE-2026-2100? Apply the vendor's patch. ## Is CVE-2026-2100 being exploited? There is no known exploitation of CVE-2026-2100 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Enterprise Linux - [CVE-2026-13757](https://insights.sbomify.com/CVE-2026-13757/): P11-kit: stack exhaustion via unbounded recursion in rpc attribute parsing (medium 6.2) - [CVE-2020-29362](https://insights.sbomify.com/CVE-2020-29362/): Memory corruption in n/a (medium 5.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-2100 and fix it if it is affected. What it is: CVE-2026-2100 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-2100 in the wild and no public exploit code. Affected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-2100/ (Markdown: https://insights.sbomify.com/CVE-2026-2100/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2100 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2100 - OSV: https://osv.dev/vulnerability/CVE-2026-2100 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-2100/ Summaries are generated and may contain mistakes; the official description above is the record.