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

Published: 2025-07-31 Last update: 2025-09-12 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-45768 is rated Moderate Risk (41/100): CVSS High severity, with low exploitation likelihood (EPSS 0.16%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-45768

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-27 0.06% 0.16% +0.10%
2 2026-04-26 0.02% 0.06% +0.04%
3 2025-08-01 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-45768

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 4.7 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-45768

OS Trackers for CVE-2025-45768

vendor priority summary link
debian unimportant CVE-2025-45768 unimportant priority: Debian including 1 source packages (pyjwt), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-45768
suse high CVE-2025-45768 severity important: SUSE including 4 source package names (python-PyJWT, python3-PyJWT, python311-PyJWT, python313-PyJWT), 77 product×package rows across 35 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (35 product lines)): Will Not Fix 77. https://www.suse.com/security/cve/CVE-2025-45768/
ubuntu medium CVE-2025-45768 medium priority: Ubuntu including 1 source packages (pyjwt), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): not-affected 7, needs-triage 1. https://ubuntu.com/security/CVE-2025-45768

Affected software / configurations for CVE-2025-45768

Vendor Product Version Raw CPE
pyjwt_project pyjwt 2.10.1 cpe:2.3:a:pyjwt_project:pyjwt:2.10.1:*:*:*:*:*:*:*

References for CVE-2025-45768

cvelogic Threat Intelligence