{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102946 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-102946 is a critical vulnerability in authlib joserfc, published on 15 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-102946 and fix it if it is affected.\n\nWhat it is: CVE-2026-102946 is a critical vulnerability in authlib joserfc, published on 15 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-102946 exists.\n\nAffected product: authlib joserfc. 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-102946/ (Markdown: https://insights.sbomify.com/CVE-2026-102946/index.md)","id":"CVE-2026-102946","markdown":"https://insights.sbomify.com/CVE-2026-102946/index.md","name":"CVE-2026-102946","record":{"aliases":["DEBIAN-CVE-2026-102946","GHSA-4pp3-559j-c5c2","UBUNTU-CVE-2026-102946","openSUSE-SU-2026:12204-1","openSUSE-SU-2026:22136-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JOSE library","requires_auth":"none","summary":"Attackers can bypass JWS signature verification by providing an empty signatures array, allowing them to forge authenticated payloads in applications using joserfc.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/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-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. Prior to 1.7.4, joserfc.jws.deserialize_json() accepts a JWS General JSON Serialization with an empty signatures array as authenticated. The verify_general_json() loop performs no iterations for the empty array and returns success because no signature check failed, allowing an attacker without a signing key to supply an arbitrary payload that relying applications may treat as authentic. The issue affects the General JSON Serialization path; compact JWS and JWT decoding, Flattened JSON serialization, and JWE JSON processing do not follow this vulnerable path. This issue is fixed in version 1.7.4.","ecosystems":["openSUSE:Leap 16.0","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"joserfc: JWS signature verification bypass via empty signatures array in jws.deserialize_json","id":"CVE-2026-102946","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Plane: Cross-Project Page Content Disclosure via PageVersionEndpoint Missing Project Scope","id":"CVE-2026-102980"},"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["1.1.0-bp160.5.1"],"introduced":["0"],"last_affected":[],"package":"python-joserfc","purl":"pkg:rpm/opensuse/python-joserfc\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:22136-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.7.7-1.1"],"introduced":["0"],"last_affected":[],"package":"python-joserfc","purl":"pkg:rpm/opensuse/python-joserfc\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:12204-1"}],"prev":{"headline":"cpp-httplib: Cookie header leaked on cross-origin redirect","id":"CVE-2026-102944"},"products":["joserfc"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["authlib"]},"summary":"Attackers can bypass JWS signature verification by providing an empty signatures array, allowing them to forge authenticated payloads in applications using joserfc.","url":"https://insights.sbomify.com/CVE-2026-102946/"}