CVE-2026-82438
Deferred Deferred - Pending Action

Cross-Origin Resource Sharing Bypass in Apache Storm

Vulnerability report for CVE-2026-82438, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: Apache Software Foundation

Description

Description Three separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP components served to an authenticated user. The Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also sending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive `Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to honour `*` together with credentials; reflecting the concrete origin removes that protection. The shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name where an initialisation parameter name was expected. The container ignored the setting and applied its own defaults, which allow credentials. Finally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET request. A script element on any origin can load such a response, which bypasses the same-origin policy entirely rather than negotiating it, and there was no way to turn the behaviour off. In each case the effect is that a page visited by an authenticated operator can read cluster, topology and log data on their behalf. Mitigation Upgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the CORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to false. Note that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such tooling should be moved to ordinary JSON requests. Users who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse proxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and rejects requests carrying a `callback` parameter. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-15
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
apache storm 3.1.0
apache storm_webapp to 3.1.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-942 The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
CWE-346 The product does not properly verify that the source of data or communication is valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Storm versions 3.0.0 before 3.1.0 allowed web pages from unrelated origins to read authenticated API responses. Three mechanisms enabled this: 1) Logviewer reflected the Origin header in Access-Control-Allow-Origin while sending Access-Control-Allow-Credentials: true, bypassing browser protections. 2) A misconfigured CORS filter applied default settings allowing credentials. 3) UI and Logviewer wrapped API responses in JSONP callbacks, bypassing same-origin policies entirely.

Detection Guidance

To detect this vulnerability, check Apache Storm Webapp versions 3.0.0 before 3.1.0 for misconfigured CORS headers and JSONP usage. Inspect HTTP responses for Access-Control-Allow-Origin reflecting the Origin header and Access-Control-Allow-Credentials: true. Also verify if JSONP callbacks are enabled by checking for callback parameters in GET requests.

Impact Analysis

An attacker could exploit this by tricking an authenticated operator into visiting a malicious web page. This page could then read sensitive data like cluster, topology, and log information on behalf of the operator. The impact includes unauthorized access to confidential system data.

Compliance Impact

This vulnerability could lead to unauthorized access and exposure of sensitive data, which may violate compliance requirements under GDPR, HIPAA, and other regulations. Unauthorized data access risks legal penalties, reputational damage, and loss of trust.

Mitigation Strategies

Immediately upgrade to Apache Storm version 3.1.0 or later. If upgrading is not possible, place the UI, Logviewer, and DRPC endpoints behind a reverse proxy that strips Access-Control-Allow-Origin and Access-Control-Allow-Credentials headers and blocks requests with callback parameters.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82438. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart