{"api_version":"1","generated_at":"2026-09-14T18:49:07+00:00","cve":"CVE-2026-82438","urls":{"html":"https://cve.report/CVE-2026-82438","api":"https://cve.report/api/cve/CVE-2026-82438.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-82438","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-82438"},"summary":{"title":"Apache Storm Webapp: Authenticated API Responses Exposed to Arbitrary Web Origins","description":"Description\n\nThree separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP\ncomponents served to an authenticated user.\n\nThe Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also\nsending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive\n`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to\nhonour `*` together with credentials; reflecting the concrete origin removes that protection.\n\nThe shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name\nwhere an initialisation parameter name was expected. The container ignored the setting and applied its own\ndefaults, which allow credentials.\n\nFinally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET\nrequest. A script element on any origin can load such a response, which bypasses the same-origin policy\nentirely rather than negotiating it, and there was no way to turn the behaviour off.\n\nIn each case the effect is that a page visited by an authenticated operator can read cluster, topology and\nlog data on their behalf.\n\nMitigation\n\nUpgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the\nCORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to\nfalse.\n\nNote that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such\ntooling should be moved to ordinary JSON requests.\n\nUsers who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse\nproxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and\nrejects requests carrying a `callback` parameter.\n\nCredit\n\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.","state":"PUBLISHED","assigner":"apache","published_at":"2026-09-14 15:17:10","updated_at":"2026-09-14 15:17:10"},"problem_types":["CWE-346","CWE-942","CWE-346 CWE-346 Origin Validation Error","CWE-942 CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains"],"metrics":[],"references":[{"url":"https://lists.apache.org/thread/2o7tl3hcdd865njxsn4d9cxp1frkctz3","name":"https://lists.apache.org/thread/2o7tl3hcdd865njxsn4d9cxp1frkctz3","refsource":"security@apache.org","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/09/13/17","name":"http://www.openwall.com/lists/oss-security/2026/09/13/17","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-82438","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-82438","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Apache Software Foundation","product":"Apache Storm Webapp","version":"affected 3.0.0 3.1.0 semver","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[{"source":"CNA","value":"The ASF using Claude Agents","lang":"en"}],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2026-09-14T14:13:42.629Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/09/13/17"}],"title":"CVE Program Container"}],"cna":{"affected":[{"collectionURL":"https://repo.maven.apache.org/maven2","defaultStatus":"unaffected","packageName":"org.apache.storm:storm-webapp","product":"Apache Storm Webapp","vendor":"Apache Software Foundation","versions":[{"lessThan":"3.1.0","status":"affected","version":"3.0.0","versionType":"semver"}]}],"credits":[{"lang":"en","type":"finder","value":"The ASF using Claude Agents"}],"descriptions":[{"lang":"en","supportingMedia":[{"base64":false,"type":"text/html","value":"<b>Description</b><br><br>Three separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP<br>components served to an authenticated user.<br><br>The Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also<br>sending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive<br>`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to<br>honour `*` together with credentials; reflecting the concrete origin removes that protection.<br><br>The shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name<br>where an initialisation parameter name was expected. The container ignored the setting and applied its own<br>defaults, which allow credentials.<br><br>Finally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET<br>request. A script element on any origin can load such a response, which bypasses the same-origin policy<br>entirely rather than negotiating it, and there was no way to turn the behaviour off.<br><br>In each case the effect is that a page visited by an authenticated operator can read cluster, topology and<br>log data on their behalf.<br><br><b>Mitigation</b><br><br>Upgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the<br>CORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to<br>false.<br><br>Note that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such<br>tooling should be moved to ordinary JSON requests.<br><br>Users who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse<br>proxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and<br>rejects requests carrying a `callback` parameter.<br><br><b>Credit</b><br><br>The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.<br>"}],"value":"Description\n\nThree separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP\ncomponents served to an authenticated user.\n\nThe Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also\nsending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive\n`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to\nhonour `*` together with credentials; reflecting the concrete origin removes that protection.\n\nThe shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name\nwhere an initialisation parameter name was expected. The container ignored the setting and applied its own\ndefaults, which allow credentials.\n\nFinally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET\nrequest. A script element on any origin can load such a response, which bypasses the same-origin policy\nentirely rather than negotiating it, and there was no way to turn the behaviour off.\n\nIn each case the effect is that a page visited by an authenticated operator can read cluster, topology and\nlog data on their behalf.\n\nMitigation\n\nUpgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the\nCORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to\nfalse.\n\nNote that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such\ntooling should be moved to ordinary JSON requests.\n\nUsers who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse\nproxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and\nrejects requests carrying a `callback` parameter.\n\nCredit\n\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm."}],"metrics":[{"other":{"content":{"text":"important"},"type":"Textual description of severity"},"scenarios":[{"lang":"en","value":"GENERAL"}]}],"problemTypes":[{"descriptions":[{"cweId":"CWE-346","description":"CWE-346 Origin Validation Error","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-942","description":"CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-09-14T14:02:07.213Z","orgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","shortName":"apache"},"references":[{"tags":["vendor-advisory"],"url":"https://lists.apache.org/thread/2o7tl3hcdd865njxsn4d9cxp1frkctz3"}],"source":{"discovery":"UNKNOWN"},"title":"Apache Storm Webapp: Authenticated API Responses Exposed to Arbitrary Web Origins","x_generator":{"engine":"Vulnogram 1.0.3"}}},"cveMetadata":{"assignerOrgId":"f0158376-9dc2-43b6-827c-5f631a4d8d09","assignerShortName":"apache","cveId":"CVE-2026-82438","datePublished":"2026-09-14T14:02:07.213Z","dateReserved":"2026-08-29T10:37:41.671Z","dateUpdated":"2026-09-14T14:13:42.629Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-14 15:17:10","lastModifiedDate":"2026-09-14 15:17:10","problem_types":["CWE-346","CWE-942","CWE-346 CWE-346 Origin Validation Error","CWE-942 CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"82438","Ordinal":"1","Title":"Apache Storm Webapp: Authenticated API Responses Exposed to Arbi","CVE":"CVE-2026-82438","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"82438","Ordinal":"1","NoteData":"Description\n\nThree separate mechanisms allowed a web page on an unrelated origin to read responses that Storm's HTTP\ncomponents served to an authenticated user.\n\nThe Logviewer reflected the request's `Origin` header back in `Access-Control-Allow-Origin` while also\nsending `Access-Control-Allow-Credentials: true`. The published security model documents a permissive\n`Access-Control-Allow-Origin: *` posture as accepted, which is safe precisely because browsers refuse to\nhonour `*` together with credentials; reflecting the concrete origin removes that protection.\n\nThe shared CORS filter used by the UI, the Logviewer and DRPC was configured with a response header name\nwhere an initialisation parameter name was expected. The container ignored the setting and applied its own\ndefaults, which allow credentials.\n\nFinally, the UI and Logviewer wrapped API responses in a caller-supplied JSONP callback for every GET\nrequest. A script element on any origin can load such a response, which bypasses the same-origin policy\nentirely rather than negotiating it, and there was no way to turn the behaviour off.\n\nIn each case the effect is that a page visited by an authenticated operator can read cluster, topology and\nlog data on their behalf.\n\nMitigation\n\nUpgrade to 3.1.0, where the Logviewer no longer reflects the request origin in a credentialed response, the\nCORS filter is configured explicitly, and JSONP wrapping is governed by `ui.enable.jsonp`, which defaults to\nfalse.\n\nNote that disabling JSONP is a behaviour change for tooling that passes a `callback` query parameter; such\ntooling should be moved to ordinary JSON requests.\n\nUsers who cannot upgrade immediately should place the UI, Logviewer and DRPC HTTP endpoints behind a reverse\nproxy that strips `Access-Control-Allow-Origin` and `Access-Control-Allow-Credentials` from responses and\nrejects requests carrying a `callback` parameter.\n\nCredit\n\nThe ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.","Type":"Description","Title":"Apache Storm Webapp: Authenticated API Responses Exposed to Arbi"}]}}}