CVE-2026-24468: OpenAEV Vulnerable to Username/Email Enumeration Through Differential HTTP Responses in Password Reset API
OpenAEV is an open source platform allowing organizations to plan, schedule and conduct cyber adversary simulation campaign and tests. Starting in version 1.11.0 and prior to version 2.0.13, the /api/reset endpoint behaves differently depending on whether the supplied username exists in the system. When a non-existent email is provided in the login parameter, the endpoint returns an HTTP 400 response (Bad Request). When a valid email is supplied, the endpoint responds with HTTP 200. This difference in server responses creates an observable discrepancy that allows an attacker to reliably determine which emails are registered in the application. By automating requests with a list of possible email addresses, an attacker can quickly build a list of valid accounts without any authentication. The endpoint should return a consistent response regardless of whether the username exists in order to prevent account enumeration. Version 2.0.13 fixes this issue.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-24468?
CVE-2026-24468 is rated as medium severity due to its potential for username and email enumeration.
How do I fix CVE-2026-24468?
To fix CVE-2026-24468, update OpenAEV to version 2.0.13 or later.
What vulnerability does CVE-2026-24468 address?
CVE-2026-24468 addresses a vulnerability that allows enumeration of usernames and emails through differential HTTP responses in the password reset API.
Which versions of OpenAEV are affected by CVE-2026-24468?
OpenAEV versions from 1.11.0 to 2.0.12 are affected by CVE-2026-24468.
Is CVE-2026-24468 exploitable remotely?
Yes, CVE-2026-24468 is exploitable remotely, allowing attackers to gather information without the need for authentication.