Security Resilience

CVE-2026-22061

Info Disclosure

Info Disclosure
Published
09 October 2026
Modified
16 October 2026
CVSS Score v4 8.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0011 1th percentile
Risk Priority 30 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-22061 is a high-severity Insertion of Sensitive Information Into Debugging Code (CWE-215) vulnerability. Its CVSS base score is 8.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 1th 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 CM-7 (Least Functionality) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

Trident versions v25.02.1 through v26.06.1 are susceptible to a vulnerability that could allow an authenticated attacker with access to debug logs to view LUKS passphrases or SMB Active Directory credentials.

CWE(s)
CWE-215

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001 Data Obfuscation Command And Control
Adversaries may obfuscate command and control traffic to make it more difficult to detect.
attack.mitre.org →
T1001.002 Steganography Command And Control
Adversaries may use steganographic techniques to hide command and control traffic to make detection efforts more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003.003 NTDS Credential Access
Adversaries may attempt to access or create a copy of the Active Directory domain database in order to steal credential information, as well as obtain other information about domain members such as devices, users, and access rights.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-0895Shared CWE-215
CVE-2025-58598Shared CWE-215
CVE-2025-34081Shared CWE-215
CVE-2026-74799Shared CWE-215
CVE-2023-21462Shared CWE-215
CVE-2025-27684Shared CWE-215
CVE-2023-49194Shared CWE-215
CVE-2026-2250Shared CWE-215
CVE-2026-44934Shared CWE-215
CVE-2025-12616Shared CWE-215

Affected Assets

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

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V13.4.2

Mitigating Controls (NIST 800-53 r5) AI

CM-7 Least Functionality partial match

Least functionality directly prohibits enabling unnecessary debug features that would expose the inserted sensitive data.

SA-11 Developer Testing and Evaluation partial match

Developer testing and evaluation will discover debug code containing sensitive information before release.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure development processes and standards stops insertion of sensitive data into debug paths.

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.DS-10 partial match
blocks

Explicitly calls for removing confidential data from processes, logs, and memory dumps that debug code commonly exposes.

PR.PS-01 partial match
blocks

Hardened configuration baselines and deployment checks can ensure debug features and associated data are disabled in production.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent developers from embedding sensitive information inside debugging statements or code paths.

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.8.19 Installation of software on operational systems partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure SDLC mandates removal of debug code and sensitive data before release.

A.8.26 Application security requirements partial match
removes
A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly prohibit embedding secrets or debug statements.

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

Security testing in development catches debug statements and sensitive data leaks.

A.8.31 Separation of development, test and production environments partial match
blocks

A.8.31 separates environments and restricts what reaches production; it does not stop sensitive information from being inserted into debugging code in the first place, so the weakness can still be present and exploitable if debugging code slips into production.

References