{"answers":{"affected":"1 open source package ship an affected version, including pyjwt. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-45768 in the wild and no public exploit code.","fix":"No fix published yet.","what":"CVE-2025-45768 is a high-severity vulnerability in n/a, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-45768 and fix it if it is affected.\n\nWhat it is: CVE-2025-45768 is a high-severity vulnerability in n/a, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-45768 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected all versions up to 2.10.1; no fix listed\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-2025-45768/ (Markdown: https://insights.sbomify.com/CVE-2025-45768/index.md)","id":"CVE-2025-45768","markdown":"https://insights.sbomify.com/CVE-2025-45768/index.md","name":"CVE-2025-45768","record":{"aliases":["CLSA-2025-1756858339","CLSA-2025-1757376737","DEBIAN-CVE-2025-45768","ECHO-3137-3dc7-eda3","GHSA-xpf8-484v-j9w6","MINI-57jg-w3p9-g2cw","PYSEC-2025-183"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JWT library","requires_auth":"none","summary":"The pyjwt library allows weak encryption due to application-chosen key lengths, potentially enabling cryptographic bypasses.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pyjwt","vendor":"pyjwt_project"}],"cvss":{"score":7,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed by the Supplier because the key length is chosen by the application that uses the library (admittedly, library users may benefit from a minimum value and a mechanism for opting in to strict enforcement).","ecosystems":["PyPI"],"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":"Weak cryptography in n/a","id":"CVE-2025-45768","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":1,"n_references":3,"next":{"headline":"php-jwt contains weak encryption","id":"CVE-2025-45769"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.10.1"],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2025-183"}],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2025-45767"},"products":["n/a"],"published":"2025-07-31","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":"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-14","vendors":["n/a"]},"summary":"The pyjwt library allows weak encryption due to application-chosen key lengths, potentially enabling cryptographic bypasses.","url":"https://insights.sbomify.com/CVE-2025-45768/"}