{"answers":{"affected":"2 open source packages ship an affected version, including jose. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34240 in the wild and no public exploit code.","fix":"Upgrade jose to 0.3.5+1 or later.","what":"CVE-2026-34240 is a high-severity authentication bypass vulnerability in appsup-dart jose, published on 31 Mar 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-34240 and fix it if it is affected.\n\nWhat it is: CVE-2026-34240 is a high-severity authentication bypass vulnerability in appsup-dart jose, published on 31 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34240 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jose (Pub): affected all versions; fixed in 0.3.5+1\n- jose (Pub): affected all versions; fixed in 0.3.5+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-34240/ (Markdown: https://insights.sbomify.com/CVE-2026-34240/index.md)","id":"CVE-2026-34240","markdown":"https://insights.sbomify.com/CVE-2026-34240/index.md","name":"CVE-2026-34240","record":{"aliases":["GHSA-vm9r-h74p-hg97"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"JOSE JavaScript library","requires_auth":"none","summary":"Attackers can forge valid JWT tokens by embedding their own public key in the header, bypassing signature verification in the JOSE library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jose","vendor":"appsup-dart"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"JOSE is a Javascript Object Signing and Encryption (JOSE) library. Prior to version 0.3.5+1, a vulnerability in jose could allow an unauthenticated, remote attacker to forge valid JWS/JWT tokens by using a key embedded in the JOSE header (jwk). The vulnerability exists because key selection could treat header-provided jwk as a verification candidate even when that key was not present in the trusted key store. Since JOSE headers are untrusted input, an attacker could exploit this by creating a token payload, embedding an attacker-controlled public key in the header, and signing with the matching private key. Applications using affected versions for token verification are impacted. This issue has been patched in version 0.3.5+1. A workaround for this issue involves rejecting tokens where header jwk is present unless that jwk matches a key already present in the application's trusted key store.","ecosystems":["Pub"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"jose vulnerable to untrusted JWK header key acceptance during signature verification","id":"CVE-2026-34240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"CtrlPanel: Stored XSS in Ticket Reply Notifications Allows Session Hijacking","id":"CVE-2026-34241"},"packages":[{"ecosystem":"Pub","fixed":["0.3.5+1"],"introduced":["0"],"last_affected":[],"package":"jose","purl":null,"source":"GHSA-vm9r-h74p-hg97"},{"ecosystem":"Pub","fixed":["0.3.5+1"],"introduced":["0"],"last_affected":[],"package":"jose","purl":"pkg:pub/jose","source":"GHSA-vm9r-h74p-hg97"}],"prev":{"headline":"Chamilo Authenticated Remote Code Execution","id":"CVE-2026-34239"},"products":["jose"],"published":"2026-03-31","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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-01","vendors":["appsup-dart"]},"summary":"Attackers can forge valid JWT tokens by embedding their own public key in the header, bypassing signature verification in the JOSE library.","url":"https://insights.sbomify.com/CVE-2026-34240/"}