Unauthenticated 2FA bypass via post-login race
Published Apr 10, 2026 · Updated Apr 10, 2026
Authentication bypass in Ajenti before 0.112 allows remote attackers to evade 2FA during a brief post-login race window. The vendor advisory identifies a race in the core plugin's 2FA flow but does not disclose the shared state, function, or synchronization error. Two-factor authentication must be enabled, and exploitation is timing-dependent; the published impact is unauthorized access with confidentiality and integrity exposure but no availability impact.
Summary
What happened
Authentication bypass in Ajenti before 0.112 allows remote attackers to evade 2FA during a brief post-login race window. The vendor advisory identifies a race in the core plugin's 2FA flow but does not disclose the shared state, function, or synchronization error. Two-factor authentication must be enabled, and exploitation is timing-dependent; the published impact is unauthorized access with confidentiality and integrity exposure but no availability impact.
The record
- CVE
- CVE-2026-40178
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Vendor
- Ajenti Project
- Product
- Ajenti
- Classifications
- CWE-362, CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 10, 2026CVE publishedPublication date reported by the CVE source.
- Apr 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.112
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo