{"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-48522 exists.","fix":"Upgrade pyjwt to 2.13.0 or later.","what":"CVE-2026-48522 is a medium-severity server-side request forgery vulnerability in jpadilla pyjwt, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-48522 and fix it if it is affected.\n\nWhat it is: CVE-2026-48522 is a medium-severity server-side request forgery vulnerability in jpadilla pyjwt, published on 28 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-48522 exists.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected all versions; fixed in 2.13.0\n- pyjwt (PyPI): affected from 2.0.0; fixed in 2.13.0\n- PyJWT (PyPI): affected from 2.0.0; fixed in 2.13.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-48522/ (Markdown: https://insights.sbomify.com/CVE-2026-48522/index.md)","id":"CVE-2026-48522","markdown":"https://insights.sbomify.com/CVE-2026-48522/index.md","name":"CVE-2026-48522","record":{"aliases":["AZL-93036","BELL-CVE-2026-48522","CLEANSTART-2026-CA24023","DEBIAN-CVE-2026-48522","ECHO-48dd-029f-8278","GHSA-993g-76c3-p5m4","MINI-43ch-j7q4-4q7g","MINI-4pv6-rpvw-8x65","MINI-6c26-3prg-6pwm","MINI-6cvv-rr78-7fcp","MINI-72mm-whg5-m9p5","MINI-7gq7-7p5q-wqcm","MINI-89gp-7gvp-f7rf","MINI-9w29-c63m-8gj6","MINI-ch2v-c4gj-fj56","MINI-cqg2-4mxx-3hjm","MINI-f3g5-5h62-g7xg","MINI-f7m5-v6r6-75j9","MINI-h4qv-qfq4-fj69","MINI-h5jj-p89w-633h","MINI-hpxh-hffj-hj53","MINI-hvch-339h-grpv","MINI-j297-gfmx-rjm7","MINI-p8mv-7279-49m3","MINI-pffq-r69g-26p3","MINI-pv99-gfxr-mvqm","MINI-q25c-27w4-69p2","MINI-r85m-vc4x-xr62","MINI-r9gg-4m6f-9q5g","MINI-v7f4-gv4h-4x48","MINI-vjp2-27f7-8gwc","MINI-vwcv-xcw3-hg7x","MINI-w4m8-f9cc-7j78","MINI-wr87-xwg2-x7hj","PYSEC-2026-175","ROOT-APP-PYPI-CVE-2026-48522","UBUNTU-CVE-2026-48522"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JWT library","requires_auth":"none","summary":"Attackers can exploit missing scheme restrictions in PyJWKClient to perform SSRF, read local files, or forge tokens if URL inputs are untrusted.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pyjwt","vendor":"pyjwt_project"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-441","name":"Unintended Proxy or Intermediary"}],"description":"PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, PyJWKClient passes its uri argument directly to urllib.request.urlopen() which uses Python stdlib's default OpenerDirector registering HTTPHandler, HTTPSHandler, FTPHandler, FileHandler, and DataHandler. There is currently no documented option to restrict which schemes PyJWKClient will fetch. If an application's jku URL ingestion path accepts attacker-influenced URLs (e.g., from JWT header, configuration file, OAuth flow parameter), the attacker can cause PyJWKClient to read arbitrary local files via file:// (SSRF on local filesystem), cause PyJWKClient to attempt FTP / data-URI fetches (broader SSRF surface), or forge tokens that PyJWT verifies as valid. The library does not directly return non-HTTP(S) URI contents to the attacker; the chained \"plant a JWKS to forge tokens\" scenario described in the original report requires additional application-layer flaws (attacker write access to a filesystem path, untrusted jku derivation) that this fix does not address. This vulnerability is fixed in 2.13.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":"PyJWKClient: missing scheme allowlist enables SSRF + token forgery via file://, ftp://, data: schemes","id":"CVE-2026-48522","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"PyJWT: Algorithm allow-list bypass when decoding with `PyJWK` / `PyJWKClient` keys","id":"CVE-2026-48523"},"packages":[{"ecosystem":"PyPI","fixed":["2.13.0"],"introduced":["2.0.0"],"last_affected":[],"package":"PyJWT","purl":null,"source":"GHSA-993g-76c3-p5m4"},{"ecosystem":"PyPI","fixed":["2.13.0"],"introduced":["0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2026-175"},{"ecosystem":"PyPI","fixed":["2.13.0"],"introduced":["2.0.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"GHSA-993g-76c3-p5m4"}],"prev":{"headline":"Null dereference in envoy","id":"CVE-2026-48521"},"products":["pyjwt"],"published":"2026-05-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-06-02","vendors":["jpadilla"]},"summary":"Attackers can exploit missing scheme restrictions in PyJWKClient to perform SSRF, read local files, or forge tokens if URL inputs are untrusted.","url":"https://insights.sbomify.com/CVE-2026-48522/"}