- Exploited
- No known exploitation
- Fix
- Fixed in 3.2.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.2.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 11/100 · provisional
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- Low (apache)
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Apache Storm's Logviewer follows symbolic links that a worker places in its own log directory, so a user who is allowed to submit topologies can read other users' worker logs and other files the Logviewer process can read. The problem appears when workers run as the topology owner.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
When workers run as the topology owner, the Logviewer serves files that a worker has placed in its own log directory as links to other files. A user who is allowed to submit topologies can read the worker logs of other users' topologies, and other files the Logviewer process can read. Users are recommended to upgrade to version 3.2.0, which fixes the issue.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects Maven packages
- Severity1/10Rated low by apache
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 33 if advisories confirm default setups are exposed
Impact
- Widely used
1 packages depend on org.apache.storm:storm-webapp.Source: deps.dev
What to do
Upgrade to a fixed version: 3.2.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-124495 (Apache Storm: Logviewer follows worker symlinks across topology ACLs), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-124495 (entry last updated 2026-11-11):
Affected:
- Maven package org.apache.storm:storm-webapp: from 3.0.0, fixed in 3.2.0
Fixed versions: 3.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124495 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124495 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/q4xbld4n4v14t8d74vb342skx8d0mzz8
- http://www.openwall.com/lists/oss-security/2026/11/11/4
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-124495
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124495"}.Timeline
- CVE published
- First seen by cve.now
- Record last updated
Affected versions
From 3.0.0 · fixed in 3.2.0
No fix released. The advisory names 3.2.0 as the fix, which the registry doesn't have yet. The latest release, 3.1.0, is still affected.
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124495
Is CVE-2026-124495 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-124495?
org.apache.storm:storm-webapp (Maven): from 3.0.0 before 3.2.0.Source: cve.now feed data
How do I fix CVE-2026-124495?
Upgrade to a fixed version: 3.2.0.Source: cve.now feed data