CVE-2026-54148

http4k: DigestAuthProvider.verify did not bind to request URI

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

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).

CVE-2026-54148 has a CVSS score of 8.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.50.0.0, 5.42.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The fix:

• Rejects credentials whose uri parameter does not match the request URL.

1. What is CVE-2026-54148? CVE-2026-54148 is a high-severity security vulnerability in org.http4k:http4k-security-digest (maven), affecting versions >= 6.0.0.0, < 6.50.0.0. It is fixed in 6.50.0.0, 5.42.0.0.
2. How severe is CVE-2026-54148? CVE-2026-54148 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.http4k:http4k-security-digest are affected by CVE-2026-54148? org.http4k:http4k-security-digest (maven) versions >= 6.0.0.0, < 6.50.0.0 is affected.
4. Is there a fix for CVE-2026-54148? Yes. CVE-2026-54148 is fixed in 6.50.0.0, 5.42.0.0. Upgrade to this version or later.
5. Is CVE-2026-54148 exploitable, and should I be worried? Whether CVE-2026-54148 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-54148 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-54148?
   • Upgrade org.http4k:http4k-security-digest to 6.50.0.0 or later
   • Upgrade org.http4k:http4k-security-digest to 5.42.0.0 or later