LowGHSA-75c5-xw7c-p5pmCVE-2024-53861PYSEC-2026-1814

PyJWT Issuer field partial matches allowed

Published 2 Dec 2024 · Updated 10 Sept 2026

Is your project on an affected pyjwt?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

pyjwtPyPI
Affected
>=2.10.0 <2.10.1
Fixed in
2.10.1
Update to the fixed version for your release line, for example:pip install 'pyjwt>=2.10.1'

Details

Summary

The wrong string if check is run for iss checking, resulting in "acb" being accepted for "_abc_".

Details

This is a bug introduced in version 2.10.0: checking the "iss" claim changed from isinstance(issuer, list) to isinstance(issuer, Sequence).

-        if isinstance(issuer, list):
+        if isinstance(issuer, Sequence):
            if payload["iss"] not in issuer:
                raise InvalidIssuerError("Invalid issuer")
        else:

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__":.

PoC

Check out the unit tests added here: https://github.com/jpadilla/pyjwt-ghsa-75c5-xw7c-p5pm

        issuer = "urn:expected"

        payload = {"iss": "urn:"}

        token = jwt.encode(payload, "secret")

        # decode() succeeds, even though `"urn:" != "urn:expected". No exception is raised.
        with pytest.raises(InvalidIssuerError):
            jwt.decode(token, "secret", issuer=issuer, algorithms=["HS256"])

Impact

I would say the real world impact is not that high, seeing as the signature still has to match. We should still fix it.

Is GHSA-75c5-xw7c-p5pm in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pyjwt, and gives you the command that fixes it.

More advisories for pyjwt

  • HighGHSA-pxh4-856f-4h89PyJWT: HS256/384/512 verify accepts empty HMAC key via oct JWK (PyJWK/PyJWKClient) enabling token forgery · 22 Oct 2026
  • MediumCVE-2026-102275PyJWT accepts inconsistent OKP x/d JWKs, causing public/private key identity confusion · 5 Oct 2026
  • MediumCVE-2026-103001PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse · 30 Sept 2026
  • MediumCVE-2026-101918PyJWT: Unauthenticated RecursionError DoS in pre-verification payload parse (PyJWKClient.get_signing_key_from_jwt / verify_signature=False) · 30 Sept 2026
  • MediumCVE-2026-102270PyJWT: ReDoS vulnerability when calling the `is_pem_format` function. · 30 Sept 2026
  • HighCVE-2026-102266PyJWT: PyJWK accepts empty HMAC keys, bypassing PyJWT's empty-key validation · 29 Sept 2026
All 25 advisories for pyjwt

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.