{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44699 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-44699 is a critical authentication bypass vulnerability in benmcollins libjwt, published on 15 May 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-44699 and fix it if it is affected.\n\nWhat it is: CVE-2026-44699 is a critical authentication bypass vulnerability in benmcollins libjwt, published on 15 May 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-44699 exists.\n\nAffected product: benmcollins libjwt. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-44699/ (Markdown: https://insights.sbomify.com/CVE-2026-44699/index.md)","id":"CVE-2026-44699","markdown":"https://insights.sbomify.com/CVE-2026-44699/index.md","name":"CVE-2026-44699","record":{"aliases":["DEBIAN-CVE-2026-44699","GHSA-q843-6q5f-w55g","UBUNTU-CVE-2026-44699"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"C JWT library","requires_auth":"none","summary":"Attackers can forge valid JWTs by exploiting algorithm confusion in libjwt, bypassing authentication in applications using RSA JWKs without alg parameters.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"LibJWT is a C JSON Web Token Library. From 3.0.0 to 3.3.2, libjwt accepts an RSA JWK that does not contain an alg parameter as the verification key for an HS256/HS384/HS512 token. In the OpenSSL backend, this causes HMAC verification to run with a zero-length key, so an attacker can forge a valid JWT without knowing any secret or RSA private key. This is an algorithm-confusion authentication bypass. It affects applications that load RSA keys from JWKS where alg is omitted, which is valid JWK syntax and common in real deployments, and then choose the verification algorithm from the JWT header, for example in a kid lookup callback. This vulnerability is fixed in 3.3.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC","id":"CVE-2026-44699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Elixir WebRTC: Missing DTLS peer fingerprint validation in ex_webrtc client-role handshake","id":"CVE-2026-44700"},"packages":[],"prev":{"headline":"Home Assistant: Cross-origin iframe access token exfiltration via WebView JS bridge callback injection","id":"CVE-2026-44698"},"products":["libjwt"],"published":"2026-05-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-05-15","vendors":["benmcollins"]},"summary":"Attackers can forge valid JWTs by exploiting algorithm confusion in libjwt, bypassing authentication in applications using RSA JWKs without alg parameters.","url":"https://insights.sbomify.com/CVE-2026-44699/"}