Low

PyJWT Issuer field partial matches allowed

  • Disclosed: 02.12.2024
  • Updated: 11.10.2026 15:17

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).

diff
-        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

python
        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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) pyjwt >= 2.10.0, < 2.10.1 2.10.1

References

CVSS score 2.2/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N
Weakness (CWE)
CWE-697
Platform
Python (PyPI)
Package
pyjwt
Disclosed
02.12.2024
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - PYSEC-2026-1814 - PyPA Advisory Database; CC BY 4.0

OSV / GitHub Advisory Database - GHSA-75c5-xw7c-p5pm - CC BY 4.0

Vulnerability history: pyjwt

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (24) in the archive
Total entries
24
First → latest
08.2017 09.2026
Without a fix
2
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 10
  • Medium 11
  • Low 2

Disclosures per year

  1. 2017: 1
  2. 2018: 0
  3. 2019: 0
  4. 2020: 0
  5. 2021: 0
  6. 2022: 1
  7. 2023: 0
  8. 2024: 1
  9. 2025: 1
  10. 2026: 20
Severity:
  1. High · 7.4 CVE-2026-102266 >= 2.13.0, < 2.14.0 2.14.0
  2. High · 7.4 CVE-2026-102273 >= 2.13.0, < 2.14.0 2.14.0
  3. High · 7.4 CVE-2026-102267 < 2.14.0 2.14.0
  4. High · 7.4 CVE-2026-102272 >= 2.13.0, < 2.14.0 2.14.0
  5. High · 7.5 CVE-2026-32597 < 2.12.0 2.12.0
  6. PyJWT Issuer field partial matches allowed this entry
    Low · 2.2 CVE-2024-53861 >= 2.10.0, < 2.10.1 2.10.1
  7. High · 7.4 CVE-2022-29217 >= 1.5.0, < 2.4.0 2.4.0
  8. High · 7.5 CVE-2017-11424 < 1.5.1 1.5.1

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.