{"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-107724 exists.","fix":"Upgrade fast-jwt to 6.3.0 or later.","what":"CVE-2026-107724 is a high-severity 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-107724 and fix it if it is affected.\n\nWhat it is: CVE-2026-107724 is a high-severity 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-107724 exists.\n\nAffected packages and fixed versions:\n- fast-jwt (npm): affected from 6.2.4; fixed in 6.3.0\n- fast-jwt (npm): affected from 6.2.4; fixed in 6.3.0\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-107724/ (Markdown: https://insights.sbomify.com/CVE-2026-107724/index.md)","id":"CVE-2026-107724","markdown":"https://insights.sbomify.com/CVE-2026-107724/index.md","name":"CVE-2026-107724","record":{"aliases":["GHSA-g3jj-5cmm-3hxx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"JavaScript JWT library","requires_auth":"none","summary":"Attackers can forge HS256 tokens by using public JWK JSON as an HMAC secret if HS256 is allowed, bypassing authentication checks.","user_interaction":"not_required","vuln_class":"security_feature_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"}],"description":"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.","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 treats raw public JWK JSON as an HMAC secret, enabling HS256 token forgery","id":"CVE-2026-107724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Hazelcast: Authorization bypass in IMap Predicates API","id":"CVE-2026-107725"},"packages":[{"ecosystem":"npm","fixed":["6.3.0"],"introduced":["6.2.4"],"last_affected":[],"package":"fast-jwt","purl":null,"source":"GHSA-g3jj-5cmm-3hxx"},{"ecosystem":"npm","fixed":["6.3.0"],"introduced":["6.2.4"],"last_affected":[],"package":"fast-jwt","purl":"pkg:npm/fast-jwt","source":"GHSA-g3jj-5cmm-3hxx"}],"prev":{"headline":"fast-jwt : Silent claim-validator bypass when JWT payload is a JSON array","id":"CVE-2026-107723"},"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 forge HS256 tokens by using public JWK JSON as an HMAC secret if HS256 is allowed, bypassing authentication checks.","url":"https://insights.sbomify.com/CVE-2026-107724/"}