How severe is CVE-2025-45768?

CVE-2025-45768 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.

Is CVE-2025-45768 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-45768?

CVE-2025-45768 affects Pyjwt Project Pyjwt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-45768?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-45768 have an EU (EUVD) identifier?

Yes. CVE-2025-45768 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23303.

When was CVE-2025-45768 published?

CVE-2025-45768 was published on 2025-07-31 and last updated on 2026-06-17.

CVE-2025-45768

CVE-2025-45768 is a high-severity vulnerability in Pyjwt Project Pyjwt with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-311.

Key facts

Severity: High (CVSS 3.x base score 7.0)
EPSS exploit prediction: 0% (6th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-23303
Weakness: CWE-311
Affected product: Pyjwt Project Pyjwt
Published: 2025-07-31
Last modified: 2026-06-17

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

Frequently asked questions

What is CVE-2025-45768?: 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).
How severe is CVE-2025-45768?: CVE-2025-45768 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.
Is CVE-2025-45768 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-45768?: CVE-2025-45768 affects Pyjwt Project Pyjwt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-45768?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-45768 have an EU (EUVD) identifier?: Yes. CVE-2025-45768 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-23303.
When was CVE-2025-45768 published?: CVE-2025-45768 was published on 2025-07-31 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:pyjwt_project:pyjwt:2.10.1:*:*:*:*:*:*:*

More vulnerabilities in Pyjwt Project Pyjwt

CVE-2026-32597 — High (CVSS 7.5): PyJWT is a JSON Web Token implementation in Python. Prior to 2.12.0, PyJWT does not validate the crit (Critical) Header…
CVE-2017-11424 — High (CVSS 7.5): In PyJWT 1.5.0 and below the `invalid_strings` check in `HMACAlgorithm.prepare_key` does not account for all PEM…
CVE-2026-48526 — High (CVSS 7.4): PyJWT is a JSON Web Token implementation in Python. Prior to 2.13.0, when the verifier is decoding JSON Web Tokens,…
CVE-2022-29217 — High (CVSS 7.4): PyJWT is a Python implementation of RFC 7519. PyJWT supports multiple different JWT signing algorithms. With JWT, an…
CVE-2026-48523 — Medium (CVSS 5.4): PyJWT is a JSON Web Token implementation in Python. From 2.9.0 to 2.12.1, there is a verifier-side algorithm allow-list…
CVE-2026-48525 — Medium (CVSS 5.3): PyJWT is a JSON Web Token implementation in Python. From 2.8.0 to 2.12.1, when verifying detached JWS tokens using the…

All CVEs affecting Pyjwt Project Pyjwt →

Other CWE-311 (Missing Encryption of Sensitive Data) vulnerabilities

CVE-2023-6339 — Critical (CVSS 10.0): Google Nest WiFi Pro root code-execution & user-data compromise
CVE-2023-4420 — Critical (CVSS 9.8): A remote unprivileged attacker can intercept the communication via e.g. Man-In-The-Middle, due to the absence of…
CVE-2023-0750 — Critical (CVSS 9.8): Yellobrik PEC-1864 implements authentication checks via javascript in the frontend interface. When the device can be…
CVE-2020-15331 — Critical (CVSS 9.8): Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded OAUTH_SECRET_KEY in /opt/axess/etc/default/axess.
CVE-2019-3431 — Critical (CVSS 9.8): All versions up to V4.01.01.02 of ZTE ZXCLOUD GoldenData VAP product have encryption problems vulnerability. Attackers…
CVE-2019-12924 — Critical (CVSS 9.8): MailEnable Enterprise Premium 10.23 was vulnerable to XML External Entity Injection (XXE) attacks that could be…

Browse all CWE-311 (Missing Encryption of Sensitive Data) vulnerabilities →