CVE-2024-12225: quarkus · Authentication Bypass Using an Alternate Path or Channel
Affects quarkusSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical.
Data as of 13 Nov 2026, 20:52 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 9.1 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| quarkus | Affected
| Fixed in– |
AI-suggested
The Red Hat advisory states that the Red Hat build of Quarkus does not include the vulnerable quarkus-security-webauthn module and is therefore not affected. For other Quarkus users, mitigation is possible by disabling the default WebAuthn REST endpoints after creating custom endpoints. This can be done by configuring the router to reject requests to the default endpoints (e.g., returning HTTP 404). Users should apply this mitigation to prevent exploitation.
Description
CVE-2024-12225 is a critical authentication bypass vulnerability in the Quarkus WebAuthn module. The module exposes default REST endpoints for user registration and login, which remain accessible even when developers create custom endpoints. This can allow attackers to obtain a login cookie that either has no associated user or impersonates an existing user by knowing only their username.