Security Resilience

CVE-2026-85864

Published
13 October 2026
Modified
13 October 2026
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0075 54th percentile
Risk Priority 58 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-85864 is a high-severity Improper Restriction of Names for Files and Other Resources (CWE-641) vulnerability. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Improper privilege management in Python allows an authorized attacker to elevate privileges locally.

CWE(s)
CWE-641

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.001 LSASS Memory Credential Access
Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS).
attack.mitre.org →
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
attack.mitre.org →
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
attack.mitre.org →
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-21361Shared CWE-641
CVE-2026-50023Shared CWE-641
CVE-2024-30063Shared CWE-641
CVE-2024-47260Shared CWE-641
CVE-2025-47173Shared CWE-641
CVE-2026-25177Shared CWE-641
CVE-2023-0046Shared CWE-641
CVE-2025-21402Shared CWE-641
CVE-2025-47953Shared CWE-641
CVE-2026-50510Shared CWE-641

Affected Assets

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation partial match

SI-10 requires validation of inputs used to construct resource names, directly stopping malformed or dangerous names from being accepted.

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 partial match
blocks

Secure SDLC practices directly require input validation and sanitization to restrict resource names derived from untrusted data.

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.

A.5.7 Threat intelligence partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure development life cycle mandates input validation and safe resource naming practices that directly prevent CWE-641.

A.8.26 Application security requirements partial match
blocks

Application security requirements include rules for handling untrusted input when constructing file or resource names.

A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates security-by-design principles (least privilege, distrust external input, fail securely, security-oriented design reviews) that reach improper name construction for some file/resource cases but leave a bounded remainder (e.g. custom business logic for name sanitization or legacy components) unaddressed by the engineering principles alone.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly require validation and sanitization of filenames derived from external input.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing can detect improper filename handling but does not itself prevent the weakness.

References