Home/CVE/CWE-307 Improper Restriction of Excessive Authentication Attempts vulnerability exists that would allow an attacker to g
CVE
CVE-2026-2402
CWE-307 Improper Restriction of Excessive Authentication Attempts vulnerability exists that would allow an attacker to g
CWE-307 Improper Restriction of Excessive Authentication Attempts vulnerability exists that would allow an attacker to gain access to the user account by performing an arbitrary number of authentication attempts with different credentials on a sequence of requests to multiple endpoints.
MEDIUM · CVSS 5.3
EPSS 0.00066
EPSS exploitation odds0.07% · top 79%
Schedule remediation
- SSVC automatable: yes - attacks can be scripted at scale
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2026-2402, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
0.07%
Top 79%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage · cisa-vulnrichment
Exploitation
none
Automatable
yes
Tech impact
partial
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LLifecycle
- 14 Apr 2026Published to NVD
- 22 Apr 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
◆
ATT&CK techniques
1Techniques this CVE enables - linked via CWE → CAPEC → ATT&CK. Pills with a solid outline are named directly in ATT&CK or Nuclei templates (high confidence); the others are linked through weakness mappings.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
7Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
CAPEC-CAPEC-16 · Dictionary-based Password Attack CAPEC-CAPEC-49 · Password Brute Forcing CAPEC-CAPEC-560 · Use of Known Domain Credentials CAPEC-CAPEC-565 · Password Spraying CAPEC-CAPEC-600 · Credential Stuffing CAPEC-CAPEC-652 · Use of Known Kerberos Credentials CAPEC-CAPEC-653 · Use of Known Operating System Credentials
⬡
Weakness Classification
▤
Affected Products & Versions
1▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-1999-1152
Compaq/Microcom 6000 Access Integrator does not disconnect a client after a cert...
same CWE-307
HIGH
CVE-1999-1324
VAXstations running Open VMS 5.3 through 5.5-2 with VMS DECwindows or MOTIF do n...
same CWE-307
CRITICAL
CVE-2001-1339
Beck IPC GmbH IPC@CHIP telnet service does not delay or disconnect users from th...
same CWE-307
CRITICAL
CVE-2001-0395
Lightwave ConsoleServer 3200 does not disconnect users after unsuccessful login ...
same CWE-307
CRITICAL
CVE-2026-2399
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traver...
same product
MEDIUM
CVE-2026-2400
CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerabilit...
same product
MEDIUM
CVE-2026-2401
CWE-532 Insertion of Sensitive Information into Log File vulnerability exists th...
same product
MEDIUM
CVE-2026-2403
CWE-1284 Improper Validation of Specified Quantity in Input vulnerability exists...
same product
MEDIUM
🔗
References & Sources
1Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.