{"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-2024-53861 exists.","fix":"Upgrade pyjwt to 2.10.1 or later.","what":"CVE-2024-53861 is a low-severity vulnerability in jpadilla pyjwt, published on 29 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-53861 and fix it if it is affected.\n\nWhat it is: CVE-2024-53861 is a low-severity vulnerability in jpadilla pyjwt, published on 29 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53861 exists.\n\nAffected packages and fixed versions:\n- pyjwt (PyPI): affected from 2.10.0; fixed in 2.10.1\n- pyjwt (PyPI): affected from 2.10.0; fixed in 2.10.1\n- PyJWT (PyPI): affected from 2.10.0; fixed in 2.10.1\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-2024-53861/ (Markdown: https://insights.sbomify.com/CVE-2024-53861/index.md)","id":"CVE-2024-53861","markdown":"https://insights.sbomify.com/CVE-2024-53861/index.md","name":"CVE-2024-53861","record":{"aliases":["GHSA-75c5-xw7c-p5pm","PYSEC-2026-1814","openSUSE-SU-2024:14540-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python JWT library","requires_auth":"high_privilege","summary":"Attackers can bypass issuer validation in pyjwt due to incorrect string comparison, potentially causing denial of service or accepting invalid tokens.","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":2.2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"description":"pyjwt is a JSON Web Token implementation in Python. An incorrect string comparison is run for `iss` checking, resulting in `\"acb\"` being accepted for `\"_abc_\"`. This is a bug introduced in version 2.10.0: checking the \"iss\" claim changed from `isinstance(issuer, list)` to `isinstance(issuer, Sequence)`. Since str is a Sequnce, but not a list, `in` is also used for string comparison. This results in `if \"abc\" not in \"__abcd__\":` being checked instead of `if \"abc\" != \"__abc__\":`. Signature checks are still present so real world impact is likely limited to denial of service scenarios. This issue has been patched in version 2.10.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["PyPI","openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Issuer field partial matches allowed in pyjwt","id":"CVE-2024-53861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"security_feature_bypass","year":"2024"},"n_packages":4,"n_references":3,"next":{"headline":"Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode","id":"CVE-2024-53862"},"packages":[{"ecosystem":"PyPI","fixed":["2.10.1"],"introduced":["2.10.0"],"last_affected":[],"package":"PyJWT","purl":null,"source":"GHSA-75c5-xw7c-p5pm"},{"ecosystem":"PyPI","fixed":["2.10.1"],"introduced":["2.10.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"GHSA-75c5-xw7c-p5pm"},{"ecosystem":"PyPI","fixed":["2.10.1"],"introduced":["2.10.0"],"last_affected":[],"package":"pyjwt","purl":"pkg:pypi/pyjwt","source":"PYSEC-2026-1814"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.10.1-1.1"],"introduced":["0"],"last_affected":[],"package":"python-PyJWT","purl":"pkg:rpm/opensuse/python-PyJWT\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:14540-1"}],"prev":{"headline":"Potential Abuse for Sending Arbitrary Emails in sp-php-email-handler","id":"CVE-2024-53860"},"products":["pyjwt"],"published":"2024-11-29","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":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"2024-12-02","vendors":["jpadilla"]},"summary":"Attackers can bypass issuer validation in pyjwt due to incorrect string comparison, potentially causing denial of service or accepting invalid tokens.","url":"https://insights.sbomify.com/CVE-2024-53861/"}