Loading...
Skip to main content
GeekWala

CVE-2026-54148 — Vulnerability in...

HIGH

http4k: `DigestAuthProvider.verify` did not bind to request URI

Published August 17, 2026Updated September 24, 2026Source: osv

Summary

### 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 [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v5.x line) | | v4.x (LTS) | **4.51.0.0** | Enterprise — contact [enterprise@http4k.org](mailto:enterprise@http4k.org) (if Digest auth is present in your v4.x line) | The fix: - Rejects credentials whose `uri` parameter 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`](https://github.com/http4k/http4k/commit/8a52b615b1) - URI binding fix: [`725f1b9697`](https://github.com/http4k/http4k/commit/725f1b9697) - Fix release: [v6.50.0.0](https://github.com/http4k/http4k/releases/tag/6.50.0.0) - Background: [RFC 7616 — HTTP Digest Access Authentication](https://datatracker.ietf.org/doc/html/rfc7616)

Advisory Timeline

  • First published August 17, 2026 (55 days ago).
  • Last revised September 24, 2026 — 38 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.http4k:http4k-security-digest to 5.42.0.0 or later
<!-- Update pom.xml dependency version to 5.42.0.0 for org.http4k:http4k-security-digest -->
Maven
Update org.http4k:http4k-security-digest to 6.50.0.0 or later
<!-- Update pom.xml dependency version to 6.50.0.0 for org.http4k:http4k-security-digest -->
Maven
Update org.http4k:http4k-security-digest to 4.51.0.0 or later
<!-- Update pom.xml dependency version to 4.51.0.0 for org.http4k:http4k-security-digest -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (3)

Affects 1 ecosystem: maven (1).

PackageEcosystemAffectedFixed In
org.http4k:http4k-security-digest
maven
5.0.0.0, 5.1.0.0, 5.1.1.0, 5.1.1.1 (+111 more)5.42.0.0
org.http4k:http4k-security-digest
maven
6.0.0.0, 6.0.1.0, 6.1.0.0, 6.1.0.1 (+87 more)6.50.0.0
org.http4k:http4k-security-digest
maven
4.10.0.0.0, 4.10.0.1, 4.10.1.0, 4.11.0.0 (+147 more)4.51.0.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

References

Frequently Asked Questions

What is CVE-2026-54148?
http4k: `DigestAuthProvider.verify` did not bind to request URI This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.1/10).
How do I check if my project is affected by CVE-2026-54148?
CVE-2026-54148 affects org.http4k:http4k-security-digest. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-54148 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.1

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-p28p-j94q-pg32

Related CVEs

More Maven advisories

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies