Skip to content

http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI

Moderate severity GitHub Reviewed Published Jun 16, 2026 in http4k/http4k • Updated Aug 17, 2026

Package

maven org.http4k:http4k-security-digest (Maven)

Affected versions

>= 5.0.0.0, < 5.42.0.0
<= 4.48.2.0
>= 6.0.0.0, < 6.50.0.0

Patched versions

5.42.0.0
6.50.0.0

Description

Impact

An issue in DigestAuthProvider.verify:

Algorithm silently forced to MD5. The configured algorithm parameter was ignored — every verification used MD5 regardless of configuration. Deployments believing they were running SHA-256 Digest auth were silently inheriting MD5's collision weaknesses, including documented attack paths against Digest schemes that rely on the hash being collision-resistant.

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 (if Digest auth is present in your v5.x line)
v4.x (LTS) 4.51.0.0 Enterprise — contact enterprise@http4k.org (if Digest auth is present in your v4.x line)

The fix:

  • Hashes with the configured algorithm instead of hardcoded MD5.

Workarounds

For deployments that cannot upgrade immediately:

  • Algorithm gap: do not rely on algorithm configuration; assume MD5 is in use and treat the Digest credentials as low-trust.

References

References

@daviddenton daviddenton published to http4k/http4k Jun 16, 2026
Published to the GitHub Advisory Database Aug 17, 2026
Reviewed Aug 17, 2026
Last updated Aug 17, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N

EPSS score

Weaknesses

Use of a Broken or Risky Cryptographic Algorithm

The product uses a broken or risky cryptographic algorithm or protocol. Learn more on MITRE.

CVE ID

CVE-2026-54147

GHSA ID

GHSA-vxxm-wwqh-mh47

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.