CVE-2025-45767: jose · Weak Cryptography
Source CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Given the absence of official patches, European organizations should take proactive steps to mitigate the risk. First, conduct an immediate inventory to identify all applications and services using jose v6.0.10. Where possible, upgrade to a later, verified secure version of the library or apply vendor-recommended patches once available. If upgrading is not immediately feasible, implement compensating controls such as network segmentation and strict access controls to limit exposure of affected systems. Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block anomalous cryptographic operations or exploitation attempts. Additionally, increase monitoring and logging around cryptographic operations to detect potential exploitation. Review cryptographic policies to ensure fallback mechanisms do not rely on weak encryption. Engage with the jose community or maintainers to clarify the dispute and obtain guidance on secure configurations. Finally, conduct security awareness training for developers to avoid using vulnerable versions and to implement cryptographic best practices.
Description
jose v6.0.10 was discovered to contain weak encryption. NOTE: this is disputed by a third party because the claim of "do not meet recommended security standards" does not reflect guidance in a final publication.
References
- github.com/panva (opens in a new tab)
- github.com/panva/jose (opens in a new tab)
- gist.github.com/ZupeiNie/705a606fbb99f3bb8c9b51e5bc13c91d (opens in a new tab)
- gist.github.com/ZupeiNie/705a606fbb99f3bb8c9b51e5bc13c91d?permalink_comment_id=5711572 (opens in a new tab)
- github.com/panva/jose/discussions/813 (opens in a new tab)
- github.com/panva/jose/blob/1e36dd29e76511e06737e5d5d500d81e01a9c3d2/src/lib/check_key_length.ts (opens in a new tab)