{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62995 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-62995 is a low-severity vulnerability in authlib joserfc, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-62995 and fix it if it is affected.\n\nWhat it is: CVE-2026-62995 is a low-severity vulnerability in authlib joserfc, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-62995 in the wild and no public exploit code.\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-62995/ (Markdown: https://insights.sbomify.com/CVE-2026-62995/index.md)","id":"CVE-2026-62995","markdown":"https://insights.sbomify.com/CVE-2026-62995/index.md","name":"CVE-2026-62995","record":{"aliases":["CLEANSTART-2026-TT52719","DEBIAN-CVE-2026-62995","GHSA-5jhw-7jv7-qcqq","UBUNTU-CVE-2026-62995","openSUSE-SU-2026:11423-1","openSUSE-SU-2026:21515-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":"low_privilege","summary":"Attackers can bypass token revocation or anti-replay protections by exploiting JWT malleability caused by non-standard padding acceptance in the joserfc library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"joserfc is a Python library that provides an implementation of several JSON Object Signing and Encryption (JOSE) standards. in versions 1.7.1 and prior,  joserfc accepts JWTs with trailing padding (==) which are not conforming to the JOSE specifications. This leads to malleability of the JWTs when consumed by joserfc. Depending on this application this might or not be an issue. This could lead to bypass of token revocation or anti-replay protection when implemented as a deny list of tokens or a deny list of token hashes. Note that ECDSA JWS are always malleable because of the malleability of ECDSA signatures (first test case in the code bellow). This makes a scheme which assumes that JWTs are not malleable brittle. However for other signatures (or MAC) schemes it might make sense to assume non malleability of the token. This issue has been fixed in version 1.7.2.","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":"none_known"},"has_fix":true,"headline":"joserfc accepts JWT with padding, leading to JWT malleability","id":"CVE-2026-62995","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Smarty Security stream restriction bypass through stream: resource","id":"CVE-2026-62996"},"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["1.1.0-bp160.4.1"],"introduced":["0"],"last_affected":[],"package":"python-joserfc","purl":"pkg:rpm/opensuse/python-joserfc\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:21515-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["1.7.4-2.1"],"introduced":["0"],"last_affected":[],"package":"python-joserfc","purl":"pkg:rpm/opensuse/python-joserfc\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:11423-1"}],"prev":{"headline":"CoreDNS `k8s_external` headless AXFR can emit an empty transfer batch that panics the `transfer` plugin","id":"CVE-2026-62994"},"products":["joserfc"],"published":"2026-07-29","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-30","vendors":["authlib"]},"summary":"Attackers can bypass token revocation or anti-replay protections by exploiting JWT malleability caused by non-standard padding acceptance in the joserfc library.","url":"https://insights.sbomify.com/CVE-2026-62995/"}