Cyber Resilience

CVE-2026-16526

Published
30 July 2026
Modified
18 August 2026
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0076 52th percentile
Risk Priority 65 floored blend · peak EPSS

Summary

CVE-2026-16526 is a high-severity File Descriptor Leak (CWE-403) vulnerability. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-39 (Process Isolation) and SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A flaw in the PCP linux_sockets module exposes an unsecured internal connection. An attacker with initial code execution can exploit this to escalate privileges and execute arbitrary commands as root.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-58280Shared CWE-403
CVE-2026-40042Shared CWE-403
CVE-2025-3032Shared CWE-403
CVE-2025-15114Shared CWE-403
CVE-2026-12296Shared CWE-403
CVE-2024-21626Shared CWE-403

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Maintains separate execution domains so file descriptors cannot be unintentionally inherited by child processes.

Prevents unintended information transfer via shared file descriptors between parent and child processes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include code reviews and static analysis that catch file-descriptor leaks before child-process invocation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can uncover descriptor leaks but does not prevent them by itself.

prevents

Secure SDLC practices include code reviews and static analysis that can detect leaked descriptors.

prevents

Secure coding rules require closing inherited file descriptors before spawning child processes.

none

Information access restriction policies may limit which processes can use descriptors, but do not address the leak itself.

References