Vulnerability in p11-kit (UBUNTU-CVE-2026-13757)

Summary

Vulnerability in p11-kit (UBUNTU-CVE-2026-13757). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.23.9-2ubuntu0.1+esm1 or later.

Original description

The description as published by the source.

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.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-13757 has been found in p11-kit.
Risk of unauthorized operations or information disclosure.
What to do: upgrade p11-kit to 0.23.9-2ubuntu0.1+esm1 or later.
If unsure, ask your IT team or search "p11-kit UBUNTU-CVE-2026-13757" on the vendor's site.

UBUNTU-CVE-2026-13757 (p11-kit)
Attack vector: local / unauthenticated / no user interaction
Patched: 0.23.9-2ubuntu0.1+esm1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in p11-kit.

📍 Affected scope

Check the vendor advisory for the affected versions of p11-kit.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.23.9-2ubuntu0.1+esm1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'p11-kit' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'p11-kit' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で p11-kit を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade p11-kit to 0.23.9-2ubuntu0.1+esm1
```
ステージング環境で 0.23.9-2ubuntu0.1+esm1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:18.04:LTS p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.9-2ubuntu0.1+esm1"}]}]

Ubuntu:Pro:20.04:LTS p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.20-1ubuntu0.1+esm1"}]}]

Ubuntu:22.04:LTS p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.24.0-6ubuntu0.1"}]}]

Ubuntu:24.04:LTS p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.25.3-4ubuntu2.2"}]}]

Ubuntu:25.10 p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:26.04:LTS p11-kit

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report access.redhat.com