CVE-2026-54148 is a high-severity (CVSS 8.1) CWE-294 vulnerability in org.http4k:http4k-security-digest. A fix is available for org.http4k:http4k-security-digest — see the affected versions and patch details below.
http4k: `DigestAuthProvider.verify` did not bind to request URI
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-54148.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-54148 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,205 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.http4k:http4k-security-digest☕org.http4k:http4k-security-digest☕org.http4k:http4k-security-digestReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
An issue in DigestAuthProvider.verify:
The uri parameter in the client's Authorization: Digest … response was not checked against the actual request URL. A captured Digest authentication response could be replayed against any other URL served by the same realm, breaking the per-request-URL binding the Digest scheme assumes.
Who is affected: any application using http4k-security-digest for HTTP Digest authentication. The bug has been present since DigestAuthProvider was introduced (commit 8a52b615b1, 2021).
Patches
| Line | Fixed in | Edition |
|---|---|---|
| v6.x (Community) | 6.50.0.0 | Community |
| v5.x (LTS) | 5.42.0.0 | Enterprise — contact [email protected] (if Digest auth is present in your v5.x line) |
| v4.x (LTS) | 4.51.0.0 | Enterprise — contact [email protected] (if Digest auth is present in your v4.x line) |
The fix:
- Rejects credentials whose
uriparameter does not match the request URL.
Workarounds
For deployments that cannot upgrade immediately:
- URI binding gap: place Digest auth behind a reverse proxy that pins requests to a single URL.
References
- Vulnerability first present:
8a52b615b1 - URI binding fix:
725f1b9697 - Fix release: v6.50.0.0
- Background: RFC 7616 — HTTP Digest Access Authentication
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.http4k:http4k-security-digest | ≥ 6.0.0.0&&< 6.50.0.0 | 6.50.0.0org.http4k:http4k-security-digest:6.50.0.0 |
| ☕Maven | org.http4k:http4k-security-digest | ≥ 5.0.0.0&&< 5.42.0.0 | 5.42.0.0org.http4k:http4k-security-digest:5.42.0.0 |
| ☕Maven | org.http4k:http4k-security-digest | ≥ 4.0.0.0&&< 4.51.0.0 | 4.51.0.0org.http4k:http4k-security-digest:4.51.0.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.http4k:http4k-security-digest, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.http4k:http4k-security-digest to 6.50.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-54148 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2026-54148 in your dependencies?
Find it across Maven, including transitive dependencies.