<?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>Sat, 03 Oct 2026 16:03:01 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-35526</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-35526</link>
      <description>cnvd-2020-35526</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-35526</guid>
    </item>
    <item>
      <title>EUVD-2026-36521</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-36521</link>
      <description>EUVD-2026-36521</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-36521</guid>
    </item>
    <item>
      <title>fkie_cve-2020-5280</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-5280</link>
      <description>&lt;p&gt;http4s before versions 0.18.26, 0.20.20, and 0.21.2 has a local file inclusion vulnerability. This vulnerability applies to all users of org.http4s.server.staticcontent.FileService, org.http4s.server.staticcontent.ResourceService and org.http4s.server.staticcontent.WebjarService. URI normalization is applied incorrectly. Requests whose path info contain ../ or // can expose resources outside of the configured location. This issue is patched in versions 0.18.26, 0.20.20, and 0.21.2. Note that 0.19.0 is a deprecated release and has never been supported.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;http4s before versions 0.18.26, 0.20.20, and 0.21.2 has a local file inclusion vulnerability. This vulnerability applies to all users of org.http4s.server.staticcontent.FileService, org.http4s.server.staticcontent.ResourceService and org.http4s.server.staticcontent.WebjarService. URI normalization is applied incorrectly. Requests whose path info contain ../ or // can expose resources outside of the configured location. This issue is patched in versions 0.18.26, 0.20.20, and 0.21.2. Note that 0.19.0 is a deprecated release and has never been supported.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-5280</guid>
    </item>
    <item>
      <title>GHSA-66q9-f7ff-mmx6 — Local file inclusion vulnerability in http4s</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-66q9-f7ff-mmx6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4s:http4s-server_2.12&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability applies to all users of:
* `org.http4s.server.staticcontent.FileService`
* `org.http4s.server.staticcontent.ResourceService`
* `org.http4s.server.staticcontent.WebjarService`&lt;/p&gt;
&lt;p&gt;#### Path escaping&lt;/p&gt;
&lt;p&gt;URI normalization is applied incorrectly.  Requests whose path info contain `../` or `//` can expose resources outside of the configured location.  Specifically:&lt;/p&gt;
&lt;p&gt;* `FileService` may expose any file on the local file system.
* `ResourceService` may expose any resource on the class path.&lt;/p&gt;
&lt;p&gt;#### Prefix matching&lt;/p&gt;
&lt;p&gt;When the service is configured with a non-empty `pathPrefix` that doesn&amp;#39;t end in a slash, any directories whose names are a prefix of `systemPath` (from `FileService`) or `pathPrefix` (from `ResourceService`) are exposed.  For example, if `pathPrefix` is `/foo` and `systemPath` is `/bar`, a request to `/foobaz/quux.txt` exposes file `/barbaz/quux.txt`, when only files beneath `/bar` should be available.&lt;/p&gt;
&lt;p&gt;#### URI decoding&lt;/p&gt;
&lt;p&gt;URI segments are not decoded before resource resolution.  This causes resources with reserved characters in their name to incorrectly return a 404.  It also may incorrectly expose the rare resource whose name is URI encoded.  This applies to `FileService`, `ResourceService`, and `WebjarService`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;In all three services, paths with an empty segment, a `.` segment, or a `..` segment are now rejected with a `400 Bad Request` response.  This fixes exposure outside the configured root.  Many clients already eliminate dot…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.http4s:http4s-server_2.12&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability applies to all users of:
* `org.http4s.server.staticcontent.FileService`
* `org.http4s.server.staticcontent.ResourceService`
* `org.http4s.server.staticcontent.WebjarService`&lt;/p&gt;
&lt;p&gt;#### Path escaping&lt;/p&gt;
&lt;p&gt;URI normalization is applied incorrectly.  Requests whose path info contain `../` or `//` can expose resources outside of the configured location.  Specifically:&lt;/p&gt;
&lt;p&gt;* `FileService` may expose any file on the local file system.
* `ResourceService` may expose any resource on the class path.&lt;/p&gt;
&lt;p&gt;#### Prefix matching&lt;/p&gt;
&lt;p&gt;When the service is configured with a non-empty `pathPrefix` that doesn&amp;#39;t end in a slash, any directories whose names are a prefix of `systemPath` (from `FileService`) or `pathPrefix` (from `ResourceService`) are exposed.  For example, if `pathPrefix` is `/foo` and `systemPath` is `/bar`, a request to `/foobaz/quux.txt` exposes file `/barbaz/quux.txt`, when only files beneath `/bar` should be available.&lt;/p&gt;
&lt;p&gt;#### URI decoding&lt;/p&gt;
&lt;p&gt;URI segments are not decoded before resource resolution.  This causes resources with reserved characters in their name to incorrectly return a 404.  It also may incorrectly expose the rare resource whose name is URI encoded.  This applies to `FileService`, `ResourceService`, and `WebjarService`.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;In all three services, paths with an empty segment, a `.` segment, or a `..` segment are now rejected with a `400 Bad Request` response.  This fixes exposure outside the configured root.  Many clients already eliminate dot…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-66q9-f7ff-mmx6</guid>
    </item>
    <item>
      <title>gsd-2020-5280</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-5280</link>
      <description>gsd-2020-5280</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-5280</guid>
    </item>
  </channel>
</rss>
