{"answers":{"affected":"2 open source packages ship an affected version, including fast-jwt.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107720 exists.","fix":"Upgrade fast-jwt to 6.3.1 or later.","what":"CVE-2026-107720 is a high-severity authentication bypass vulnerability in nearform fast-jwt, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-107720 and fix it if it is affected.\n\nWhat it is: CVE-2026-107720 is a high-severity authentication bypass vulnerability in nearform fast-jwt, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107720 exists.\n\nAffected packages and fixed versions:\n- fast-jwt (npm): affected all versions; fixed in 6.3.1\n- fast-jwt (npm): affected all versions; fixed in 6.3.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-107720/ (Markdown: https://insights.sbomify.com/CVE-2026-107720/index.md)","id":"CVE-2026-107720","markdown":"https://insights.sbomify.com/CVE-2026-107720/index.md","name":"CVE-2026-107720","record":{"aliases":["GHSA-8wpc-h4q6-8fxv"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"JWT library","requires_auth":"none","summary":"Attackers can bypass authentication by submitting unsigned JWTs when the verifier is configured with an empty key and explicit algorithms.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.1, fast-jwt createVerifier accepts an unsigned JWT when key is an empty string or null and algorithms is a non-empty allowlist. Falsy synchronous keys bypass prepareKeyOrSecret, allowedAlgorithms remains active, hasKey is false, and the empty signature avoids the verifySignature gate. An attacker can therefore submit a token containing arbitrary claims without possessing a signing key, resulting in authentication or authorization bypass. Claim validators still run, and non-empty keys, an empty key without algorithms, and the async key resolver path do not have this behavior. This issue is fixed in version 6.3.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"fast-jwt: createVerifier accepts unsigned JWTs when key is '' or null and algorithms is explicitly set","id":"CVE-2026-107720","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"fast-jwt clockTolerance: Infinity silently bypasses both exp and nbf validation (and persists in the verifier cache)","id":"CVE-2026-107721"},"packages":[{"ecosystem":"npm","fixed":["6.3.1"],"introduced":["0"],"last_affected":[],"package":"fast-jwt","purl":null,"source":"GHSA-8wpc-h4q6-8fxv"},{"ecosystem":"npm","fixed":["6.3.1"],"introduced":["0"],"last_affected":[],"package":"fast-jwt","purl":"pkg:npm/fast-jwt","source":"GHSA-8wpc-h4q6-8fxv"}],"prev":{"headline":"fast-jwt: Verifier cache accepts expired JWTs without iat.","id":"CVE-2026-107719"},"products":["fast-jwt"],"published":"2026-10-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-09","vendors":["nearform"]},"summary":"Attackers can bypass authentication by submitting unsigned JWTs when the verifier is configured with an empty key and explicit algorithms.","url":"https://insights.sbomify.com/CVE-2026-107720/"}