CVE-2025-63811

Exp

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.

Published: 2025-11-12 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-63811 is rated Exploit Available (50.3/100): CVSS High severity, with low exploitation likelihood (EPSS 0.24%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2025-63811

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

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

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-06-15 0.02% 0.24% +0.22%
2 2026-04-21 0.05% 0.02% -0.03%
3 2026-01-19 — 0.05% —

Full EPSS history (4 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-63811

GitHub Security Advisory for CVE-2025-63811

GHSA-9mj6-hxhv-w67j · Severity: high · Ecosystem: go — jose2go is vulnerable to a JWT bomb attack through its decode function

OS Trackers for CVE-2025-63811

vendor priority summary link
debian not yet assigned CVE-2025-63811 not yet assigned priority: Debian including 1 source packages (golang-github-dvsekhvalnov-jose2go), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-63811
ubuntu medium CVE-2025-63811 medium priority: Ubuntu including 1 source packages (golang-github-dvsekhvalnov-jose2go), 8 status rows across 8 suites (bionic, focal, jammy, noble, plucky, questing, upstream, xenial): needs-triage 7, ignored 1. https://ubuntu.com/security/CVE-2025-63811

Affected software / configurations for CVE-2025-63811

Vendor Product Version Raw CPE
dvsekhvalnov jose2go >= 1.5.0, < 1.7.0 cpe:2.3:a:dvsekhvalnov:jose2go:*:*:*:*:*:go:*:*

References for CVE-2025-63811

URL Tags
https://github.com/dvsekhvalnov/jose2go/issues/33 Exploit Issue Tracking Mitigation
cvelogic Threat Intelligence