Answer in brief
CVE-2026-54147 records a Medium severity (CVSS 6.5) vulnerability in http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI. The current sources do not mark it as known exploited. The current feed maps http4k/http4k (generic), org.http4k:http4k-security-digest (maven), org.http4k:http4k-security-digest (maven), org.http4k:http4k-security-digest (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps http4k/http4k (generic), org.http4k:http4k-security-digest (maven), org.http4k:http4k-security-digest (maven), org.http4k:http4k-security-digest (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| http4k/http4kgeneric | < 4.51.0.0 || >= 5.0.0.0, < 5.42.0.0 || >= 6.0.0.0, < 6.50.0.0 | Not reported |
| org.http4k:http4k-security-digestmaven | >=5.0.0.0,<5.42.0.0 | 5.42.0.0 |
| org.http4k:http4k-security-digestmaven | <=4.48.2.0 | Not reported |
| org.http4k:http4k-security-digestmaven | >=6.0.0.0,<6.50.0.0 | 6.50.0.0 |
| org.http4k:http4k-security-digestmaven | >=6.0.0.0 <6.50.0.0 | 6.50.0.0 |
| org.http4k:http4k-security-digestmaven | >=5.0.0.0 <5.42.0.0 | 5.42.0.0 |
| org.http4k:http4k-security-digestmaven | >=0 | Not reported |
Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 17, 2026
http4k is a functional toolkit for Kotlin HTTP applications. Prior to 4.51.0.0, 5.42.0.0, and 6.50.0.0, DigestAuthProvider.verify in http4k-security-digest ignores its configured algorithm parameter and verifies every Digest response with hardcoded MD5. Deployments configured for SHA-256 therefore receive weaker MD5-based verification, exposing Digest authentication to collision-related attack paths that depend on the hash function's collision resistance. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.
Quoted source text, attributed separately from HOL analysis.