CVE-2026-24468 OpenAEV Vulnerable to Username/Email Enumeration Through Differential HTTP Responses in Password Reset API
An attacker can enumerate valid user accounts by observing differential HTTP responses in the password reset API, facilitating targeted attacks.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-24468?
CVE-2026-24468 is a medium-severity vulnerability in OpenAEV-Platform openaev, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-204
Which versions are affected by CVE-2026-24468?
How do I fix CVE-2026-24468?
No fix has been published for CVE-2026-24468 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-24468 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24468 exists.
Sources
Also known as GHSA-v6rg-hf9w-f8ph.