What is the CVSS score of EUVD-2026-83030?

EUVD-2026-83030 has a CVSS 3.1 base score of 4.2 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a patch available for EUVD-2026-83030?

Yes, a patch is available for EUVD-2026-83030. Update the affected software to the latest version immediately.

WebSphere Application Server EUVD-2026-83030

| CVE-2026-10841 MEDIUM

HTTP Request/Response Smuggling (CWE-444)

2026-09-18 ibm

GHSA-6734-h858-25gr

Information Disclosure IBM Request Smuggling Websphere Application Server Cics Tx Advanced

4.2

CVSS 3.1 · Vendor: ibm

Severity by source

Vendor (ibm) PRIMARY

4.2 MEDIUM

AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

vuln.today AI

4.2 MEDIUM

Network-reachable smuggling but AC:H due to proxy/WebSphere parser-desync dependency; kept vendor PR:L and partial C:L/I:L with no availability impact, scope unchanged.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Metadata Corrected

Sep 18, 2026 - 17:40 vuln.today

tag: Websphere Application Server added

Analysis Generated

Sep 18, 2026 - 16:44 vuln.today

CVE Published

Sep 18, 2026 - 16:06 nvd

MEDIUM 4.2

DescriptionCVE.org

IBM WebSphere Application Server 8.5, 9.0, and Liberty are vulnerable to HTTP request smuggling.

AnalysisAI

HTTP request smuggling (CWE-444) in IBM WebSphere Application Server 8.5, 9.0, and Liberty lets an authenticated, low-privileged remote attacker desynchronize HTTP request framing between WebSphere and an intermediary so that one user's request boundaries are misattributed on a shared connection. The issue only manifests when WebSphere sits behind or in front of a second HTTP parser (reverse proxy, load balancer, or CDN) that disagrees with WebSphere on Content-Length versus Transfer-Encoding chunked handling; a standalone WebSphere instance with no fronting or backend HTTP hop is not affected, and the 4.2 score reflects high attack complexity, partial confidentiality and integrity impact, and no availability or scope change. …

Unlock full vulnerability intelligence

Risk assessment & exploitation conditions
Attack chain visualization
Remediation with exact patch versions
Threat intelligence from 22 sources
Personal watchlist & email alerts

Continue with Google Continue with GitHub

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access

technique details hidden

Delivery

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Access

technique details hidden

Delivery

technique details hidden

Exploit

technique details hidden

Execution

technique details hidden

Impact

technique details hidden

Vulnerability AssessmentAI

Exploitation	Exploitation requires WebSphere Application Server 8.5, 9.0, or Liberty deployed behind (or in front of) an intermediary - a reverse proxy, load balancer, or CDN - whose HTTP request framing (Content-Length vs Transfer-Encoding chunked handling) can be desynchronized from WebSphere's parser; smuggling has no effect on a single WebSphere instance with no fronting/backend HTTP hop. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment	This is a genuine-but-low-priority issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario	Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation	Patch available per vendor advisory: IBM has published the remediation at https://www.ibm.com/support/pages/node/7287740, which lists the interim fix or fix pack for WebSphere Application Server 8.5 and 9.0 and the corresponding Liberty fix pack - apply the level named there, since no exact fix version is exposed in the CVE metadata and should not be assumed. … Detailed patch versions, workarounds, and compensating controls in full report.