<?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, 09 Oct 2026 12:33:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-10549</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-10549</link>
      <description>EUVD-2026-10549</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-10549</guid>
    </item>
    <item>
      <title>fkie_cve-2023-51442</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-51442</link>
      <description>&lt;p&gt;Navidrome is an open source web-based music collection server and streamer. A security vulnerability has been identified in navidrome&amp;#39;s subsonic endpoint, allowing for authentication bypass. This exploit enables unauthorized access to any known account by utilizing a JSON Web Token (JWT) signed with the key &amp;#34;not so secret&amp;#34;. The vulnerability can only be exploited on instances that have never been restarted. Navidrome supports an extension to the subsonic authentication scheme, where a JWT can be provided using a `jwt` query parameter instead of the traditional password or token and salt (corresponding to resp. the `p` or `t` and `s` query parameters). This authentication bypass vulnerability potentially affects all instances that don&amp;#39;t protect the subsonic endpoint `/rest/`, which is expected to be most instances in a standard deployment, and most instances in the reverse proxy setup too (as the documentation mentions to leave that endpoint unprotected). This issue has been patched in version 0.50.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Navidrome is an open source web-based music collection server and streamer. A security vulnerability has been identified in navidrome&amp;#39;s subsonic endpoint, allowing for authentication bypass. This exploit enables unauthorized access to any known account by utilizing a JSON Web Token (JWT) signed with the key &amp;#34;not so secret&amp;#34;. The vulnerability can only be exploited on instances that have never been restarted. Navidrome supports an extension to the subsonic authentication scheme, where a JWT can be provided using a `jwt` query parameter instead of the traditional password or token and salt (corresponding to resp. the `p` or `t` and `s` query parameters). This authentication bypass vulnerability potentially affects all instances that don&amp;#39;t protect the subsonic endpoint `/rest/`, which is expected to be most instances in a standard deployment, and most instances in the reverse proxy setup too (as the documentation mentions to leave that endpoint unprotected). This issue has been patched in version 0.50.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-51442</guid>
    </item>
    <item>
      <title>GHSA-wq59-4q6r-635r — Authentication bypass vulnerability in navidrome's subsonic endpoint</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wq59-4q6r-635r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/navidrome/navidrome&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A security vulnerability has been identified in navidrome&amp;#39;s subsonic endpoint, allowing for authentication bypass. This exploit enables unauthorized access to any known account by utilizing a JSON Web Token (JWT) signed with the key &amp;#34;not so secret&amp;#34;.&lt;/p&gt;
&lt;p&gt;The vulnerability can only be exploited on instances that have never been restarted.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Navidrome supports an extension to the subsonic authentication scheme, where a JWT can be provided using a `jwt` query parameter instead of the traditional password or token and salt (corresponding to resp. the `p` or `t` and `s` query parameters).&lt;/p&gt;
&lt;p&gt;During the first initialization, navidrome generates a random key that is then used by the authentication module to validate JWTs before extracting the username from the `sub` claim. If for some reason the key cannot be retrieved by the initialization code, a hardcoded value is used instead: &amp;#34;not so secret&amp;#34;.&lt;/p&gt;
&lt;p&gt;A bug in the order of operations during navidrome startup results in the authentication module initializing before the module responsible for generating and persisting the random key. As a consequence, the authentication module falls back to using the hardcoded value, which remains in use until the instance gets restarted. Additionally, an error that was meant to be logged when the fallback value is used does not get logged due to another bug, preventing the operator from becoming aware of the issue.&lt;/p&gt;
&lt;p&gt;The flaw allows the creation of a JWT with the `sub` claim set to an…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/navidrome/navidrome&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;A security vulnerability has been identified in navidrome&amp;#39;s subsonic endpoint, allowing for authentication bypass. This exploit enables unauthorized access to any known account by utilizing a JSON Web Token (JWT) signed with the key &amp;#34;not so secret&amp;#34;.&lt;/p&gt;
&lt;p&gt;The vulnerability can only be exploited on instances that have never been restarted.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;Navidrome supports an extension to the subsonic authentication scheme, where a JWT can be provided using a `jwt` query parameter instead of the traditional password or token and salt (corresponding to resp. the `p` or `t` and `s` query parameters).&lt;/p&gt;
&lt;p&gt;During the first initialization, navidrome generates a random key that is then used by the authentication module to validate JWTs before extracting the username from the `sub` claim. If for some reason the key cannot be retrieved by the initialization code, a hardcoded value is used instead: &amp;#34;not so secret&amp;#34;.&lt;/p&gt;
&lt;p&gt;A bug in the order of operations during navidrome startup results in the authentication module initializing before the module responsible for generating and persisting the random key. As a consequence, the authentication module falls back to using the hardcoded value, which remains in use until the instance gets restarted. Additionally, an error that was meant to be logged when the fallback value is used does not get logged due to another bug, preventing the operator from becoming aware of the issue.&lt;/p&gt;
&lt;p&gt;The flaw allows the creation of a JWT with the `sub` claim set to an…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wq59-4q6r-635r</guid>
    </item>
    <item>
      <title>gsd-2023-51442</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-51442</link>
      <description>gsd-2023-51442</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-51442</guid>
    </item>
  </channel>
</rss>
