How to Fix CVE-2026-2332: Inconsistent interpretation of http requests in Eclipse Jetty

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

What is CVE-2026-2332?

In Eclipse Jetty, the HTTP/1.1 parser is vulnerable to request smuggling when chunk extensions are used, similar to the "funky chunks" techniques outlined here: * https://w4ke.info/2025/06/18/funky-chunks.html * https://w4ke.info/2025/10/29/funky-chunks-2.html Jetty terminates chunk extension parsing at \r\n inside quoted strings instead of treating this as an error. POST / HTTP/1.1 Host: localhost Transfer-Encoding: chunked 1;ext="val X 0 GET /smuggled HTTP/1.1 ... Note how the chunk extension does not close the double quotes, and it is able to inject a smuggled request.

Am I affected?

Run the version check that matches your platform:

# Linux
dpkg -s eclipse 2>/dev/null | grep -i version
rpm -q eclipse 2>/dev/null
eclipse --version 2>/dev/null

Compare what you see against the Affected row above (Eclipse Foundation Eclipse Jetty 12.1.0 to <12.1.6, 12.0.0 to <12.0.32, 11.0.0 to <11.0.27, 10.0.0 to <10.0.27, 9.4.0 to <9.4.59). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-2332

The primary fix is to upgrade Eclipse Jetty to the patched build. Use the commands for your platform below; the patched versions listed in the vendor advisory are: Eclipse Jetty 12.1.6; Eclipse Jetty 12.0.32; Eclipse Jetty 11.0.27; Eclipse Jetty 10.0.27 (and 1 more SKUs — see vendor advisory).

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade eclipse
eclipse --version 2>/dev/null || dpkg -s eclipse | grep -i version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --security eclipse -y
rpm -q eclipse

SUSE / openSUSE

sudo zypper patch --category security
rpm -q eclipse

Complete PowerShell remediation script (Windows)

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

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-2332-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] Detecting installed version of Eclipse Jetty"
    $pkg = winget list --id "Eclipse_Jetty" 2>$null
    Write-Host $pkg

    Write-Host "[2/4] Backing up 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] Applying upgrade to Eclipse Jetty 12.1.6; Eclipse Jetty 12.0.32; Eclipse Jetty 11.0.27; Eclipse J..."
    winget upgrade --id "Eclipse_Jetty" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "Eclipse_Jetty"
    Write-Host "Fix 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-2332 affecting Eclipse Jetty
# Detect -> backup -> upgrade -> verify -> log.

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

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

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

echo "[3/4] Applying upgrade (target: Eclipse Jetty 12.1.6; Eclipse Jetty 12.0.32; Eclipse Jetty 11.0.27; Eclipse J...)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y eclipse
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y eclipse
elif command -v yum >/dev/null; then
    yum update -y eclipse
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

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

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)

# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Service-level fallback

# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop eclipse
sudo systemctl disable eclipse

How to verify the fix worked

# Linux
eclipse --version 2>/dev/null || dpkg -s eclipse | grep -i version
rpm -q eclipse 2>/dev/null || true

# Windows
winget list | findstr /I "eclipse"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Eclipse Jetty 12.1.6; Eclipse Jetty 12.0.32; Eclipse Jetty 11.0.27; Eclipse Jetty 10.0.27 (and 1 more SKUs, see vendor advisory). Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

Related fixes

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

• How to Fix CVE-2026-1195: Critical Vulnerability in MineAdmin , Critical Vulnerability in MineAdmin
• How to Fix CVE-2026-21695: Critical Vulnerability in titra , Critical Vulnerability in titra
• How to Fix CVE-2026-41488: CWE-918: Server-Side Request Forgery (SSRF) in langchain-openai , CWE-918: Server-Side Request Forgery (SSRF) in langchain-openai
• How to Fix CVE-2026-39388: Cwe-295: improper certificate validation in openbao , Cwe-295: improper certificate validation in openbao
• How to Fix CVE-2026-26830: Command Injection in n/a , Command Injection in n/a

Is CVE-2026-2332 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

7.4 (high). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

• Official vendor advisory: https://gitlab.eclipse.org/security/cve-assignment/-/issues/89
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2332
• https://github.com/jetty/jetty.project/security/advisories/GHSA-355h-qmc2-wpwf

*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.*