CVE-2025-63811: n/a
Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 10/25/2026, 04:40:10 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubdvsekhvalnov/jose2gopkg:github/dvsekhvalnov/jose2goOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
1. Monitor network traffic and application logs for anomalous JWE tokens exhibiting unusually high compression ratios or sizes. 2. Implement rate limiting and throttling on endpoints that process JWE tokens to reduce the risk of resource exhaustion. 3. Employ Web Application Firewalls (WAFs) or API gateways capable of detecting and blocking suspicious token payloads. 4. Where possible, disable or restrict support for compressed JWE tokens until a patch is available. 5. Engage with the jose2go maintainers or community to track patch releases and apply updates promptly once available. 6. Conduct thorough testing of token processing components under load to identify potential resource exhaustion scenarios. 7. Consider deploying resource quotas or container limits to prevent a single process from consuming excessive system resources. 8. Educate development and security teams about this vulnerability to ensure secure token handling practices.
Description
An issue was discovered in dvsekhvalnov jose2go 1.5.0 thru 1.7.0 allowing an attacker to cause a Denial-of-Service (DoS) via crafted JSON Web Encryption (JWE) token with an exceptionally high compression ratio.
Impact
For European organizations, the primary impact of CVE-2025-63811 is the potential disruption of services that rely on jose2go for JWE token processing. This can lead to denial-of-service conditions, causing downtime or degraded performance of critical applications, including identity management, API gateways, and secure communications. The availability impact could affect customer-facing services, internal authentication systems, and any microservices architecture components that use jose2go. Given the vulnerability does not affect confidentiality or integrity, data breaches are unlikely; however, service unavailability can lead to operational disruptions, reputational damage, and financial losses. Organizations in sectors such as finance, healthcare, and government, which often use secure token-based authentication, may face heightened risks. Additionally, the lack of patches increases exposure time, emphasizing the need for proactive defenses. The ease of remote exploitation without authentication or user interaction further elevates the threat level.
Weaknesses
- CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.