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

published 2026-10-13 30d ago modified 2026-10-16 26d ago also EUVD-2026-98960

cvss: 9.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits: 0; none known

Is CVE-2026-52394 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: total
Assessed: 29d ago (2026-10-13)

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

gist.github.com https://gist.github.com/CAPTAIN1275/48a0b7d67d0e58cb05c607e0d715447c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-209 Generation of Error Message Containing Sensitive Information

References

Sources

CVE List CVE-2026-52394
NVD CVE-2026-52394

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.