Description
Description

The Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For
daemon logs those settings were not applied: the access decision combined the "this is a daemon log" flag
with the authorizer result in a way that discarded the authorizer's answer whenever the flag was set, and
the daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any
user able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the
other daemon logs on every reachable node, which contain other tenants' topology names, owners and
configuration fragments.

The same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so
`/listLogs` and `/searchLogs` returned every tenant's topology and worker log file names regardless of the
caller. That part is metadata only.

There was no configuration that closed either behaviour.

Mitigation

Upgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the
worker log paths already used, and the listing endpoints filter by the requesting user.

Users who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the
daemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user.

Credit

The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
Published: 2026-09-14
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized access to daemon logs revealing sensitive topology and configuration data
Action: Patch immediately
AI Analysis

Impact

The Logviewer component of Apache Storm implements access controls for user and group based log reading. However, for daemon logs the access decision mistakenly drops the authorization check whenever the "daemon log" flag is set, and the corresponding endpoints bypass the authorizer entirely. As a result, any entity able to satisfy the servlet filter can read the content of logs such as nimbus.log, supervisor.log, and other system logs. In addition, the log listing endpoints accept user input but ignore it, returning the full set of tenant log file names to every caller. These are purely metadata, but combined with the raw log data expose detailed configuration fragments and topology names missing or incorrectly applied authorization validation (CWE‑862).

Affected Systems

Apache Software Foundation: Apache Storm Logviewer. All deployments using the Logviewer component prior to version 3.1.0 are affected. The specific affected code paths are the daemon log page and download handlers, as well as the /listLogs and /searchLogs endpoints. No version matrix is provided beyond the recommendation to upgrade, so any installation of the Logviewer that includes daemon log handling is at risk.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate severity. The EPSS score is <1%, indicating a very low but nonzero exploitation probability, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is any user who can reach the Logviewer service and satisfy the servlet filter, which may include remotely reachable clients or internal actors. The absence of a configuration knob to disable the exposed behavior means the risk remains unless mitigated by patching or additional network controls.

Generated by OpenCVE AI on September 21, 2026 at 00:17 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Storm Logviewer to version 3.1.0 or later, which enforces user and group lists on
  • If an upgrade is not immediately feasible, place the Logviewer behind a reverse proxy that restricts access to the daemon log endpoints to trusted IP ranges or authenticated sessions
  • Treat the daemon log content as readable only by users who have already passed filter‑level authentication, reducing the potential exposure of sensitive log data

Generated by OpenCVE AI on September 21, 2026 at 00:17 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 14 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 14 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Description Description The Logviewer offers `logs.users` and `logs.groups` so operators can control who may read log content. For daemon logs those settings were not applied: the access decision combined the "this is a daemon log" flag with the authorizer result in a way that discarded the authorizer's answer whenever the flag was set, and the daemon log page and download endpoints reached the handler without consulting an authorizer at all. Any user able to pass the configured servlet filter could therefore read `nimbus.log`, `supervisor.log` and the other daemon logs on every reachable node, which contain other tenants' topology names, owners and configuration fragments. The same advisory covers the log listing endpoints, which accepted a user argument and never applied it, so `/listLogs` and `/searchLogs` returned every tenant's topology and worker log file names regardless of the caller. That part is metadata only. There was no configuration that closed either behaviour. Mitigation Upgrade to 3.1.0, where the daemon log paths evaluate the same configured user and group lists that the worker log paths already used, and the listing endpoints filter by the requesting user. Users who cannot upgrade immediately should place the Logviewer behind a reverse proxy that restricts the daemon log endpoints, and should treat daemon log content as readable by any filter-authenticated user. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
Title Apache Storm Logviewer: Log Access Controls Not Enforced by Logviewer
Weaknesses CWE-862
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-09-14T19:54:36.871Z

Reserved: 2026-08-29T10:35:33.225Z

Link: CVE-2026-82437

cve-icon Vulnrichment

Updated: 2026-09-14T14:13:39.910Z

cve-icon NVD

Status : Deferred

Published: 2026-09-14T15:17:10.757

Modified: 2026-09-14T20:58:48.430

Link: CVE-2026-82437

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T00:30:06Z

Weaknesses