dbcve.org
Hardened ImagesApplication · Redhat

CVE-2026-13757

MEDIUM · 6.2 CVSS v3.1 Published 2026-06-29
Fix available
A fix is available. Upgrade to after 4.22.1 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack exhaustion vulnerability exists in p11-kit's RPC message attribute parsing functions (p11_rpc_message_get_attribute and p11_rpc_message_get_attribute_array_value) due to unbounded mutual recursion when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send deeply nested template attributes to exhaust the stack and crash the service.

MitigationRestrict access to the p11-kit RPC Unix domain socket and implement recursion depth limiting in the template attribute parsing functions to prevent stack exhaustion from deeply nested requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hardened ImagesApplication
Affected:all versions
Openshift Container PlatformApplication
Affected:>= 4.0, <= 4.22.1
Enterprise LinuxOperating system
Affected:= 6.0= 7.0= 8.0= 9.0= 10.0
P11 KitApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify p11-kit is installed
    Run 'p11-kit --version' or check package manager (rpm -q p11-kit, dpkg -l p11-kit)
    Affected if Any version of p11-kit is installed - all versions are affected by this CVE
  2. Check if p11-kit RPC socket exists
    Look for Unix domain socket at /run/p11-kit/p11-kit.rpc or similar path (ls -la /run/p11-kit/ or ps aux | grep p11-kit)
    Affected if The RPC socket exists and is accessible - this is the attack vector
  3. Verify socket permissions allow local access
    Check socket file permissions (ls -la /run/p11-kit/p11-kit.rpc) and confirm other users can access it
    Affected if Socket has permissive permissions (e.g., world-readable/writable) allowing local unauthenticated access
  4. Confirm RPC server is running
    Check running processes for p11-kit server (ps aux | grep -i p11) or check if socket is active
    Affected if p11-kit RPC service is actively running and accepting connections
  5. Check Red Hat Enterprise Linux version
    Run 'cat /etc/redhat-release' or 'hostnamectl'
    Affected if Running RHEL 6.0, 7.0, 8.0, 9.0, or 10.0 - all listed as affected versions
  6. Check Red Hat OpenShift Container Platform version
    Run 'oc get clusterversion' or check cluster version
    Affected if Running OpenShift version 4.0 through 4.22.1 - these versions are affected

Your environment is affected if p11-kit is installed and the RPC Unix domain socket is accessible to local users, regardless of version since all versions contain the vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.22.1
Interim mitigation

Restrict access to the p11-kit RPC Unix domain socket and implement recursion depth limiting in the template attribute parsing functions to prevent stack exhaustion from deeply nested requests.

Fix this in Hardened Images Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13757 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13757 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data