{"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-102275 exists.","fix":"Upgrade pyjwt to 2.15.0 or later.","what":"CVE-2026-102275 is a medium-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-102275 and fix it if it is affected.\n\nWhat it is: CVE-2026-102275 is a medium-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-102275 exists.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected from 2.1.0; fixed in 2.15.0\n- pyjwt (PyPI): affected from 2.1.0; fixed in 2.15.0\n- PyJWT (PyPI): affected from 2.1.0; fixed in 2.15.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-102275/ (Markdown: https://insights.sbomify.com/CVE-2026-102275/index.md)","id":"CVE-2026-102275","markdown":"https://insights.sbomify.com/CVE-2026-102275/index.md","name":"CVE-2026-102275","record":{"aliases":["AZL-105233","CLEANSTART-2026-QX32909","CLEANSTART-2026-WH43251","DEBIAN-CVE-2026-102275","ECHO-5c06-a158-9d54","GHSA-x33g-cr3x-6449","MINI-24qq-9pcw-w9gg","MINI-2gc5-5jpj-hvpv","MINI-2m3c-fp28-4649","MINI-57jj-59jg-p7rc","MINI-5j2x-jprm-754c","MINI-68jm-wjv2-7rcx","MINI-74f6-wxpx-2p4m","MINI-7grc-fgv7-w8px","MINI-7pg7-hxw5-xvh7","MINI-8f4v-p4cf-5m6h","MINI-c3f3-g2g5-m625","MINI-cp2h-94w5-4p43","MINI-h2w6-f6q2-358q","MINI-h3w9-hvhc-jxrh","MINI-j8mc-6f56-rqc2","MINI-jj8j-jx9r-9pq4","MINI-p3jh-xx5x-fqmx","MINI-r2r5-pffr-3jvx","MINI-r8w5-gh4r-64h3","MINI-vfwm-6pv7-p36r","MINI-vmjx-jxxc-88mp","MINI-w968-4fvh-6f78","MINI-wc66-wrg9-vpm9","MINI-wc95-x2h8-v5rx","PYSEC-2026-4183","UBUNTU-CVE-2026-102275"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Python JWT library","requires_auth":"none","summary":"Attackers can bypass token validation by exploiting inconsistent OKP JWK components, allowing use of stolen tokens without the legitimate private key.","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":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in  jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.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 accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion","id":"CVE-2026-102275","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":"brace-expansion: DoS via uncontrolled recursion in parseCommaParts causing stack exhaustion","id":"CVE-2026-102276"},"packages":[{"ecosystem":"PyPI","fixed":["2.15.0"],"introduced":["2.1.0"],"last_affected":[],"package":"PyJWT","purl":null,"source":"GHSA-x33g-cr3x-6449"},{"ecosystem":"PyPI","fixed":["2.15.0"],"introduced":["2.1.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"GHSA-x33g-cr3x-6449"},{"ecosystem":"PyPI","fixed":["2.15.0"],"introduced":["2.1.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2026-4183"}],"prev":{"headline":"PyJWT: Malformed RSA JWK aborts parsing of an entire JWK Set","id":"CVE-2026-102274"},"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 BOM Bypass","id":"CVE-2026-102272","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":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["jpadilla"]},"summary":"Attackers can bypass token validation by exploiting inconsistent OKP JWK components, allowing use of stolen tokens without the legitimate private key.","url":"https://insights.sbomify.com/CVE-2026-102275/"}