CVE-2026-54147 is a medium-severity (CVSS 6.5) vulnerability in org.http4k:http4k-security-digest. O3 Security confirms whether CVE-2026-54147 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI
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:
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 [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:
- Hashes with the configured
algorithminstead of hardcoded MD5.
Workarounds
For deployments that cannot upgrade immediately:
- Algorithm gap: do not rely on
algorithmconfiguration; assume MD5 is in use and treat the Digest credentials as low-trust.
References
- Vulnerability first present:
8a52b615b1 - Algorithm fix:
65d23d99fc - 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.0 |
| ☕Maven | org.http4k:http4k-security-digest | ≥ 5.0.0.0&&< 5.42.0.0 | 5.42.0.0 |
| ☕Maven | org.http4k:http4k-security-digest | all versions | No fix |
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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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-54147 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.
How O3 protects you
O3 pinpoints whether CVE-2026-54147 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-54147. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-54147 in your dependencies?
O3 detects CVE-2026-54147 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.