Security Resilience

CVE-2026-52394

Info Disclosure

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

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-52394 is a critical-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability in Deepseek (inferred from references). Its CVSS base score is 9.1 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 34th 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 AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

DeepSeek V4 is vulnerable to Incorrect Access Control via a crafted input.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1078 Valid Accounts Stealth
Adversaries may obtain and abuse credentials of existing accounts as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1078.002 Domain Accounts Stealth
Adversaries may obtain and abuse credentials of a domain account as a means of gaining Initial Access, Persistence, Privilege Escalation, or Defense Evasion.
T1087 Account Discovery Discovery
Adversaries may attempt to get a listing of valid accounts, usernames, or email addresses on a system or within a compromised environment.
T1187 Forced Authentication Credential Access
Adversaries may gather credential material by invoking or forcing a user to automatically provide authentication information through a mechanism in which they can intercept.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
T1552.001 Credentials In Files Credential Access
Adversaries may search local file systems and remote file shares for files containing insecurely stored credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-28117Shared CWE-201, CWE-209
CVE-2026-44226Shared CWE-209
CVE-2024-26270Shared CWE-201
CVE-2023-37306Shared CWE-209
CVE-2025-40653Shared CWE-209
CVE-2024-35690Shared CWE-201
CVE-2026-56331Shared CWE-209
CVE-2026-86409Shared CWE-201
CVE-2024-32796Shared CWE-201
CVE-2026-91882Shared CWE-209

Affected Assets

Deepseek
—
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)
  • 1 hardening rule · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)
  • V14.2.3
  • V16.5.1

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.

Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.

si-11 directly requires error messages to avoid revealing exploitable information about the system or its data.

Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.

DE.CM-09 partial match
blocks

Monitoring runtime data flows and outputs can detect sensitive data being transmitted.

PR.DS-02 partial match
blocks

Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.

PR.DS-10 partial match
blocks

Protecting data-in-use includes removing confidential values before they are processed or sent.

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

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.

finds

Security testing can detect error messages that leak sensitive information.

blocks

A.8.12's DLP tools can detect and block outbound transmissions containing sensitive data patterns (e.g., credentials in error messages, email addresses in API responses), masking the code defect during egress, but the application-level weakness remains and many instances — internal transmissions, novel data formats like heap addresses, legitimate API responses to authorized recipients within the trust boundary — fall outside DLP's monitored channels.

prevents

Secure-coding standards explicitly forbid hard-coded or unfiltered sensitive data in outbound messages.

removes

A.8.9's templates and configuration enforcement can remove configuration-level instances of CWE-209 (e.g., disabling verbose error pages, suppressing debug output, setting generic error responses), but cannot reach the majority of instances where application code explicitly constructs error messages containing sensitive data — those require code changes the clause does not perform.

References