CVE-2026-56450

Home/CVE/AIL did not restrict repeated failed attempts to verify a two-factor authentication (OTP) code. An attacker who had reac

CVE

↯ PDF report

AIL did not restrict repeated failed attempts to verify a two-factor authentication (OTP) code. An attacker who had reac

AIL did not restrict repeated failed attempts to verify a two-factor authentication (OTP) code. An attacker who had reached the 2FA verification step, such as after successfully completing the password-authentication stage, could submit an unlimited number of OTP guesses. This could enable brute-force guessing of a valid code and bypass the intended second authentication factor, resulting in unauthorized account access.

The patch introduces per-user failed-OTP tracking, blocks verification after 30 failed attempts for one hour, clears the counter after a successful OTP verification, and provides administrator recovery actions to purge affected lockouts.

Monitor

⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)

No Sigma yet — build one → YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2026-56450, 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).

▣

Severity & exploitation scoring

EPSS exploitation probability

n/a

No EPSS score in our data for this CVE. EPSS is published daily for scored CVEs - a very new, reserved, or rejected CVE may not have one yet.

CVSS metric silhouette

No structured CVSS vector for this CVE. Older entries often have only a numeric base score - the metric breakdown radar requires a full AV:_/AC:_/... vector string published by NVD.

SSVC triage · cisa-vulnrichment

Exploitation

none

Automatable

Tech impact

partial

Attack path

Full kill chain

→

◆

ATT&CK techniques

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.

T1078 · Valid Accounts T1110.001 · Password Guessing^2× T1110.003 · Password Spraying T1110.004 · Credential Stuffing T1558 · Steal or Forge Kerberos Tickets

▤ Build a SIEM detection for these techniques

▤

CAPEC attack patterns

Attack 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

CWE-307Improper Restriction of Excessive Authentication Attempts

▤

Related CVEs

CVEs 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... 1 same CWE-307 CRITICAL CVE-2001-0395 Lightwave ConsoleServer 3200 does not disconnect users after unsuccessful login ... same CWE-307 CRITICAL

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://github.com/ail-project/ail-framework/commit/d3a394fe68fd5aeee86f3a3c91d4a0350f91e974