https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-02T10:43:58.685823+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-372011 EUVD-2026-372011 2026-10-02T10:43:58.687829+00:00 EUVD-2026-372011 https://cve.radiocsirt.org/vuln/fkie_cve-2026-54147 fkie_cve-2026-54147 2026-10-02T10:43:58.687859+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-vxxm-wwqh-mh47 GHSA-vxxm-wwqh-mh47 — http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI 2026-10-02T10:43:58.687893+00:00

Affected: Maven: org.http4k:http4k-security-digest

### 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](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: - 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

- Vulnerability first present: [`8a52b615b1`](https://github.com/http4k/http4k/commit/8a52b615b1) - Algorithm fix: [`65d23d99fc`](https://github.com/http4k/http4k…