<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 10:43:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-372011</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-372011</link>
      <description>EUVD-2026-372011</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-372011</guid>
    </item>
    <item>
      <title>fkie_cve-2026-54147</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-54147</link>
      <description>&lt;p&gt;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&amp;#39;s collision resistance. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;s collision resistance. This issue is fixed in versions 4.51.0.0, 5.42.0.0, and 6.50.0.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-54147</guid>
    </item>
    <item>
      <title>GHSA-vxxm-wwqh-mh47 — http4k: `DigestAuthProvider.verify` ignored configured algorithm and did not bind to request URI</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vxxm-wwqh-mh47</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4k:http4k-security-digest&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An issue in `DigestAuthProvider.verify`:&lt;/p&gt;
&lt;p&gt;**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&amp;#39;s collision weaknesses, including documented attack paths against Digest schemes that rely on the hash being collision-resistant.&lt;/p&gt;
&lt;p&gt;**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).&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;| 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) |&lt;/p&gt;
&lt;p&gt;The fix:
- Hashes with the configured `algorithm` instead of hardcoded MD5.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Vulnerability first present: [`8a52b615b1`](https://github.com/http4k/http4k/commit/8a52b615b1)
- Algorithm fix: [`65d23d99fc`](https://github.com/http4k/http4k…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4k:http4k-security-digest&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An issue in `DigestAuthProvider.verify`:&lt;/p&gt;
&lt;p&gt;**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&amp;#39;s collision weaknesses, including documented attack paths against Digest schemes that rely on the hash being collision-resistant.&lt;/p&gt;
&lt;p&gt;**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).&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;| 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) |&lt;/p&gt;
&lt;p&gt;The fix:
- Hashes with the configured `algorithm` instead of hardcoded MD5.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;- Vulnerability first present: [`8a52b615b1`](https://github.com/http4k/http4k/commit/8a52b615b1)
- Algorithm fix: [`65d23d99fc`](https://github.com/http4k/http4k…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vxxm-wwqh-mh47</guid>
    </item>
  </channel>
</rss>
