CVE-2026-19863
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.
CVE-2026-19863
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-19863
Structured affected-version data
Original package identities and version rules from this source.
[
{
"vendor": "Eclipse Foundation",
"versions": [
{
"status": "affected",
"version": "12.1.0",
"versionType": "semver",
"lessThanOrEqual": "12.1.12"
}
],
"packageName": "org.eclipse.jetty:jetty-ethereum",
"collectionURL": "https://repo.maven.apache.org/maven2/",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-19863
Source reference:
/cveMetadata/cveId
Publisher severity
critical
Source reference: /containers/cna/metrics
- Event
- #28708 · Revision 1
- Added to Heist Feed
- Publisher date