<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-11T10:42:36.028487+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-107724</id>
    <title>fkie_cve-2026-107724</title>
    <updated>2026-10-11T10:42:36.057865+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.2.4, fast-jwt can classify raw serialized public JWK or JWKS JSON as an HMAC secret because src/crypto.js performDetectPublicKeyAlgorithms treats non-PEM strings as symmetric key material. If HS256 is explicitly allowed or inferred, an attacker who knows the exact serialized public-key bytes can use those bytes as an HMAC key and create a token containing arbitrary claims that createVerifier accepts. Serialization ordering or whitespace differences can prevent exploitation, and applications using supported PEM keys with an asymmetric-only algorithm allowlist are not affected. This issue is fixed in version 6.3.0.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-107724"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-g3jj-5cmm-3hxx</id>
    <title>GHSA-g3jj-5cmm-3hxx — fast-jwt treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery</title>
    <updated>2026-10-11T10:42:36.057969+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: fast-jwt</p>
<p>### Summary</p>
<p>`fast-jwt` 6.2.4 silently classifies raw serialized public JWK JSON
as an HMAC secret.</p>
<p>If an application supplies public JWK JSON text as the verifier key and
HS256 is explicitly allowed or automatically inferred, an attacker who
knows the same public JSON text can use it as an HMAC key and create an
arbitrary HS256 token that `fast-jwt` accepts as valid.</p>
<p>This can result in authentication or authorization bypass through forged
JWT claims.</p>
<p>The PoC demonstrates the issue with a serialized RSA public JWK. The same
non-PEM classification also applies to raw JWKS JSON text, although the
attached standalone PoC focuses on the smallest JWK case.</p>
<p>### Details</p>
<p>The verifier accepts a string or Buffer as key material. In
`src/crypto.js`, `performDetectPublicKeyAlgorithms()` attempts to infer
the permitted algorithm family from the supplied string.</p>
<p>Strings matching supported PEM public-key formats are classified as
asymmetric keys. Any other non-empty string is assumed to be an HMAC
secret:</p>
<p>```js
function performDetectPublicKeyAlgorithms(key) {
  const trimmedKey = key.trim()
  const publicKeyPemMatch = trimmedKey.match(publicKeyPemMatcher)</p>
<p>if (trimmedKey.match(privateKeyPemMatcher)) {
    throw new TokenError(
      TokenError.codes.invalidKey,
      'Private keys are not supported for verifying.'
    )
  } else if (
    publicKeyPemMatch &amp;&amp;
    publicKeyPemMatch[1] === 'RSA'
  ) {
    return rsaAlgorithms
  } else if (
    !publicKeyPemMatch &amp;&amp;
    !trimmedKey.in…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-g3jj-5cmm-3hxx"/>
  </entry>
</feed>
