CVE-2025-63811: An issue was discovered in dvsekhvalnov jose2go 1.5.0 thru 1.7.0 allowing an attacker to cause a Denial-of-Ser

This week

HIGH 7.5REMOTEUPGRADE

CVE-2025-63811 is a high-severity flaw (CVSS 7.5) affecting jose2go. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-400
Published	2025-11-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: dvsekhvalnov

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-11-12 18:15 UTCPublished CVE record published
2026-06-17 09:53 UTCUpdated Record last modified

dvsekhvalnov jose2go UPGRADE

Affected: >= 1.5.0 and < 1.7.0

Fixed in: 1.7.0

Safe to downgrade to: a release before 1.5.0

1. Check installed version

apt-cache policy jose2go || rpm -q jose2go || jose2go --version

2. UPGRADE to 1.7.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jose2go

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jose2go

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.5.0 (Debian / Ubuntu)

apt-cache madison jose2go sudo apt install jose2go=<VERSION_BEFORE_1.5.0> sudo apt-mark hold jose2go

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list jose2go sudo dnf downgrade jose2go-<VERSION_BEFORE_1.5.0> sudo dnf versionlock add jose2go

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Advisories and coverage

Official advisories

HashiCorp Vault Releases: v2.2.0 2026-10-15
HashiCorp Vault Releases: v2.2.0-rc1 2026-10-08

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-63811?

jose2go: upgrade to 1.7.0. Exact commands for each OS are on this page.

Is CVE-2025-63811 being exploited?

CVE-2025-63811 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-63811 affect?

CVE-2025-63811 affects jose2go. Severity is high (CVSS 7.5). 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.

How urgent is CVE-2025-63811?

Priority 41/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2023-50658 HIGH 7.5 UPGRADE The jose2go component before 1.6.0 for Go allows attackers to cause a denial of service (CPU consumption) via

References

← Back to latest CVEs