Vulnerability in io.undertow:undertow-parent (CVE-2026-28368)
Summary
Vulnerability in io.undertow:undertow-parent (CVE-2026-28368). Confidential information can be exposed externally.
Original description
The description as published by the source.
A flaw was found in Undertow. This vulnerability allows a remote attacker to construct specially crafted requests where header names are parsed differently by Undertow compared to upstream proxies. This discrepancy in header interpretation can be exploited to launch request smuggling attacks, potentially bypassing security controls and accessing unauthorized resources.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-28368 has been found in io.undertow:undertow-parent.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "io.undertow:undertow-parent CVE-2026-28368" on the vendor's site.
CVE-2026-28368 (io.undertow:undertow-parent) — CWE-444 / CVSS v3 8.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-444) exists in io.undertow:undertow-parent.
Check the vendor advisory for the affected versions of io.undertow:undertow-parent.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで io.undertow:undertow-parent を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-28368 undertow
- Ubuntu UBUNTU-CVE-2026-28368 undertow
References
- advisory nvd.nist.gov
- package github.com
- patch secalert@redhat.com
- patch secalert@redhat.com
- web secalert@redhat.com
- web secalert@redhat.com
- web github.com