Cyber Resilience

CVE-2026-49427

Published
19 August 2026
Modified
20 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.0027 20th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2026-49427 is a high-severity Premature Release of Resource During Expected Lifetime (CWE-826) vulnerability in Freebsd (inferred from references). Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 20th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Pages belonging to largepage shared memory objects were not explicitly wired. When sendfile(2) transmitted such an object with the SF_NOCACHE flag, it freed the underlying pages after transmission even though existing mappings still referred to them. An unprivileged local user…

more

can abuse the bug to access freed kernel memory. This can be exploited to escalate privileges.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-51727Shared CWE-826
CVE-2025-24912Shared CWE-826
CVE-2024-58249Shared CWE-826
CVE-2026-31663Shared CWE-826
CVE-2023-1297Shared CWE-826
CVE-2026-45984Shared CWE-826
CVE-2026-53322Shared CWE-826
CVE-2026-33526Shared CWE-826
CVE-2026-32748Shared CWE-826
CVE-2025-31115Shared CWE-826

Affected Assets

Freebsd
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover premature-release defects before deployment.

Engineering principles can require correct resource lifetime management so the premature-release pattern is never coded.

Process isolation confines the blast radius when a resource is released while still referenced inside another domain.

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 development practices directly address coding errors that release resources while they are still needed.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover instances of premature resource release after code is deployed.

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 detect premature-release bugs, providing partial mitigation.

prevents

Secure development lifecycle practices can include resource-lifetime checks that reduce premature-release defects.

prevents

Application security requirements can mandate explicit resource-release rules, partially addressing the weakness.

prevents

Secure architecture principles encourage proper resource scoping and lifetime management.

prevents

Secure coding standards directly prohibit premature resource release, covering most of the weakness.

References