CVE-2026-19863: Security vulnerability
An unauthenticated client may access certain protected resources when using EthereumAuthenticator if the request path contains the configured login path.
This is caused by the authenticator using an unanchored substring match when identifying the login page. If the login path appears later within a protected request path, the request may be treated as the login page and its authentication or role requirement replaced with ALLOWED.
Exploitation requires the protected resource path to contain the configured login path as a later segment. Explicitly FORBIDDEN routes are not affected.
Event History
Frequently Asked Questions
Which routes are exposed to unauthenticated access?
Protected routes are exposed only when their path contains the configured login path later in the path, causing the route to be handled as a login page. Routes explicitly configured as FORBIDDEN are not affected.
What must an attacker do to exploit this issue?
An attacker only needs to make an unauthenticated request to a protected resource whose path includes the configured login path as a later segment. No authentication is required for the bypass condition described.
How can I identify potentially affected routes?
Review the configured login path and compare it with protected resource paths. Any protected path that contains that login path after the beginning of the request path may have its authentication or role requirement replaced with ALLOWED.