● High · CVSS 7.5

How to Fix CVE-2026-1605: Denial of service via resource consumption in Eclipse Jetty

Q: What is the CVSS score for CVE-2026-1605?

7.5 (High). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`.

Q: Where is the official advisory for CVE-2026-1605?

The vendor advisory is at [https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f](https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-1605.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-1605 is a denial of service via resource consumption in Eclipse Foundation Eclipse Jetty. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	7.5 (High)
Actively exploited?	No public listing in CISA KEV
Affected	Eclipse Jetty 12.0.0 to <=12.0.31; Eclipse Jetty 12.1.0. to <=12.1.5
Fixed in	See vendor advisory
Type (CWE)	CWE-400 Uncontrolled Resource Consumption

What is CVE-2026-1605?

In Eclipse Jetty, versions 12.0.0-12.0.31 and 12.1.0-12.0.5, class GzipHandler exposes a vulnerability when a compressed HTTP request, with Content-Encoding: gzip, is processed and the corresponding response is not compressed.

This happens because the JDK Inflater is allocated for decompressing the request, but it is not released because the release mechanism is tied to the compressed response.

In this case, since the response is not compressed, the release mechanism does not trigger, causing the leak. The CVSS base score is 7.5 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f.

Am I affected?

Check the version of Eclipse Jetty you are running and compare it against the Affected row above (Eclipse Jetty 12.0.0 to <=12.0.31; Eclipse Jetty 12.1.0. to <=12.1.5). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s eclipse-jetty 2>/dev/null | grep -i ^Version
rpm -q eclipse-jetty 2>/dev/null
command -v eclipse-jetty >/dev/null && eclipse-jetty --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Eclipse Jetty*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Eclipse Jetty" 2>$null

How to fix CVE-2026-1605

Upgrade Eclipse Jetty to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade eclipse-jetty
dpkg -s eclipse-jetty | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh eclipse-jetty -y
# or for older releases:
sudo yum update eclipse-jetty -y
rpm -q eclipse-jetty

SUSE / openSUSE


sudo zypper refresh
sudo zypper update eclipse-jetty
rpm -q eclipse-jetty

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-1605 affecting Eclipse Jetty
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-1605-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Eclipse Jetty*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\eclipse-jetty-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Eclipse Jetty" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Eclipse Jetty" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Eclipse Jetty"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-1605 affecting Eclipse Jetty
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-1605-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s eclipse-jetty 2>/dev/null | grep -i ^Version || echo "eclipse-jetty not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q eclipse-jetty || echo "eclipse-jetty not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-1605-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/eclipse-jetty /etc/eclipse-jetty.d /etc/eclipse-jetty.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y eclipse-jetty
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y eclipse-jetty
elif command -v yum >/dev/null; then
    yum update -y eclipse-jetty
elif command -v zypper >/dev/null; then
    zypper --non-interactive update eclipse-jetty
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s eclipse-jetty 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q eclipse-jetty
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-1605" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-1605"

Disable the affected service (Linux)


sudo systemctl stop eclipse-jetty 2>/dev/null || true
sudo systemctl disable eclipse-jetty 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s eclipse-jetty 2>/dev/null | grep -i ^Version
rpm -q eclipse-jetty 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Eclipse Jetty*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-2960: Stack buffer overflow in DWR-M960 — Stack buffer overflow in DWR-M960
How to Fix CVE-2026-20761: Command injection in SmartServer IoT — Command injection in SmartServer IoT
How to Fix CVE-2026-0808: Critical Vulnerability in Spin Wheel – Interactive spinning wheel that offers coupons , Critical Vulnerability in Spin Wheel – Interactive spinning wheel that offers coupons
How to Fix CVE-2026-2519: External control of assumed-immutable web parameter flaw in Online Scheduling and Appointment Booking System – Bookly , External control of assumed-immutable web parameter flaw in Online Scheduling and Appointment Booking System – Bookly
How to Fix CVE-2026-3862: Cross-Site Scripting Vulnerability in SiteMinder Administrative UI , Cross-Site Scripting Vulnerability in SiteMinder Administrative UI

Is CVE-2026-1605 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-1605?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-1605?

7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Where is the official advisory for CVE-2026-1605?

The vendor advisory is at https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-1605.

References

Official vendor advisory: https://github.com/jetty/jetty.project/security/advisories/GHSA-xxh7-fcf3-rj7f
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1605
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*