{"answers":{"affected":"3 open source packages ship an affected version, including pyjwt and PyJWT. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102272 exists.","fix":"Upgrade pyjwt to 2.14.0 or later.","what":"CVE-2026-102272 is a high-severity vulnerability in jpadilla pyjwt, published on 28 Sep 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-102272 and fix it if it is affected.\n\nWhat it is: CVE-2026-102272 is a high-severity vulnerability in jpadilla pyjwt, published on 28 Sep 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-102272 exists.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected from 2.13.0; fixed in 2.14.0\n- pyjwt (PyPI): affected from 2.13.0; fixed in 2.14.0\n- PyJWT (PyPI): affected from 2.13.0; fixed in 2.14.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-102272/ (Markdown: https://insights.sbomify.com/CVE-2026-102272/index.md)","id":"CVE-2026-102272","markdown":"https://insights.sbomify.com/CVE-2026-102272/index.md","name":"CVE-2026-102272","record":{"aliases":["AZL-105224","CLEANSTART-2026-GJ26931","CLEANSTART-2026-YQ31003","DEBIAN-CVE-2026-102272","ECHO-20d5-2851-e01f","GHSA-r6x4-923q-g947","MINI-2chf-753x-64x4","MINI-2p9h-qh8j-frhv","MINI-42r5-78p5-5v39","MINI-49p6-36pm-ppqp","MINI-4gcj-26rw-48w3","MINI-5252-8w5c-gwxm","MINI-7jjp-qr53-gf44","MINI-84x3-4rpv-qc6x","MINI-9mjh-hx2j-wmr9","MINI-hc57-pr3j-g8x5","MINI-p6vf-cxvr-962g","MINI-q9xp-pqqc-8gf7","MINI-vc2x-gxf7-jqp9","MINI-xc72-c54p-27qc","PYSEC-2026-4150","ROOT-APP-PYPI-CVE-2026-102272","UBUNTU-CVE-2026-102272"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JWT library","requires_auth":"none","summary":"Attackers can forge authenticated tokens by exploiting a BOM parsing flaw in PyJWT's key detection, bypassing signature verification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pyjwt","vendor":"pyjwt_project"}],"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":"PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, HMACAlgorithm.prepare_key in jwt/algorithms.py is affected because raw-JWK detector does not normalize accepted Unicode byte-order marks before checking for JSON. This occurs when a public JWK is prefixed with a UTF-8 BOM and used in a mixed-algorithm verification path. As a result, public JWK bypasses asymmetric-key detection and becomes the HMAC secret. Consequently, an attacker who knows the public key can forge authenticated tokens. This issue is fixed in version 2.14.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"PyJWT BOM Bypass","id":"CVE-2026-102272","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"PyJWT accepts public JWK containers as HMAC secrets","id":"CVE-2026-102273"},"packages":[{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["2.13.0"],"last_affected":[],"package":"PyJWT","purl":null,"source":"GHSA-r6x4-923q-g947"},{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["2.13.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"GHSA-r6x4-923q-g947"},{"ecosystem":"PyPI","fixed":["2.14.0"],"introduced":["2.13.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2026-4150"}],"prev":{"headline":"PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard","id":"CVE-2026-102271"},"products":["pyjwt"],"published":"2026-09-28","related":[{"cvss_score":9.1,"headline":"PyJWT: Asymmetric-PEM detection bypass: whitespace/line-ending-mutated public keys skip the HS/asymmetric confusion guard","id":"CVE-2026-102268","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":7.5,"headline":"PyJWT accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)","id":"CVE-2026-32597","kev_date_added":null,"published":"2026-03-12"},{"cvss_score":7.4,"headline":"PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation","id":"CVE-2026-102266","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":7.4,"headline":"PyJWT: PyJWKClient follows redirects when fetching JWKS","id":"CVE-2026-102267","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":7.4,"headline":"PyJWT: Public keys in DER form are accepted as HMAC secrets, bypassing the CVE-2022-29217 guard","id":"CVE-2026-102271","kev_date_added":null,"published":"2026-09-28"},{"cvss_score":7.4,"headline":"PyJWT accepts public JWK containers as HMAC secrets","id":"CVE-2026-102273","kev_date_added":null,"published":"2026-09-28"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["jpadilla"]},"summary":"Attackers can forge authenticated tokens by exploiting a BOM parsing flaw in PyJWT's key detection, bypassing signature verification.","url":"https://insights.sbomify.com/CVE-2026-102272/"}