<?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:03:27 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233911</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233911</link>
      <description>EUVD-2026-233911</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233911</guid>
    </item>
    <item>
      <title>fkie_cve-2022-31142</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-31142</link>
      <description>&lt;p&gt;@fastify/bearer-auth is a Fastify plugin to require bearer Authorization headers. @fastify/bearer-auth prior to versions 7.0.2 and 8.0.1 does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack. Version 7.0.2 and 8.0.1 of @fastify/bearer-auth contain a patch. There are currently no known workarounds. The package fastify-bearer-auth, which covers versions 6.0.3 and prior, is also vulnerable starting at version 5.0.1. Users of fastify-bearer-auth should upgrade to a patched version of @fastify/bearer-auth.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;@fastify/bearer-auth is a Fastify plugin to require bearer Authorization headers. @fastify/bearer-auth prior to versions 7.0.2 and 8.0.1 does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack. Version 7.0.2 and 8.0.1 of @fastify/bearer-auth contain a patch. There are currently no known workarounds. The package fastify-bearer-auth, which covers versions 6.0.3 and prior, is also vulnerable starting at version 5.0.1. Users of fastify-bearer-auth should upgrade to a patched version of @fastify/bearer-auth.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-31142</guid>
    </item>
    <item>
      <title>GHSA-376v-xgjx-7mfr — fastify-bearer-auth vulnerable to Timing Attack Vector</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-376v-xgjx-7mfr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fastify-bearer-auth, npm: @fastify/bearer-auth&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;fastify-bearer-auth does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack.&lt;/p&gt;
&lt;p&gt;All versions of fastify-bearer-auth are also affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;We released:&lt;/p&gt;
&lt;p&gt;* v8.0.1 with a fix for the Fastify v4 line
* v7.0.2 with a fix for the Fastify v3 line&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds. Update your dependencies.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://hackerone.com/reports/1633287&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/fastify/fastify-bearer-auth](https://github.com/fastify/fastify-bearer-auth)
* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: fastify-bearer-auth, npm: @fastify/bearer-auth&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;fastify-bearer-auth does not securely use crypto.timingSafeEqual. A malicious attacker could estimate the length of one valid bearer token. According to the corresponding RFC 6750, the bearer token has only base64 valid characters, reducing the range of characters for a brute force attack.&lt;/p&gt;
&lt;p&gt;All versions of fastify-bearer-auth are also affected.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;We released:&lt;/p&gt;
&lt;p&gt;* v8.0.1 with a fix for the Fastify v4 line
* v7.0.2 with a fix for the Fastify v3 line&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds. Update your dependencies.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;https://hackerone.com/reports/1633287&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Open an issue in [https://github.com/fastify/fastify-bearer-auth](https://github.com/fastify/fastify-bearer-auth)
* Email us at [hello@matteocollina.com](mailto:hello@matteocollina.com)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-376v-xgjx-7mfr</guid>
    </item>
    <item>
      <title>gsd-2022-31142</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-31142</link>
      <description>gsd-2022-31142</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-31142</guid>
    </item>
  </channel>
</rss>
