CVE-2026-82437
MediumCVSS 4.3Exploitation Probability (EPSS)
Low risk19th percentile - higher than 19% of all known CVEs
Summary
In Apache Storm's Logviewer, the `logs.users` and `logs.groups` access controls were not applied to daemon logs — the authorization decision was overridden by the "this is a daemon log" flag, and the daemon log page and download endpoints reached the handler without consulting an authorizer at all. Additionally, the `/listLogs` and `/searchLogs` endpoints accepted a user argument but never applied it, returning every tenant's log file names. The issue was fixed in version 3.1.0.
Risk Assessment
Any user able to pass the configured servlet filter could read `nimbus.log`, `supervisor.log` and other daemon logs on every reachable node, exposing other tenants' topology names, owners and configuration fragments. No configuration existed that closed this behavior.
Recommendation
Upgrade Apache Storm to version 3.1.0, where daemon log paths evaluate the configured user and group lists and the listing endpoints filter by the requesting user. If an immediate upgrade is not possible, place the Logviewer behind a reverse proxy that restricts the daemon log endpoints and treat daemon log content as readable by any filter-authenticated user.
Related vulnerabilities
- CVE-2026-63774Critical
Insufficient input validation in the PowerSYSTEM Center report designer allows an authenticated user to execute unauthorized SQL commands.
- CVE-2026-63017Critical
Incorrect authorization in PowerSYSTEM Center allows a low-privileged, authenticated user to access resources normally limited to administrators.
- CVE-2026-77596Critical
In Kubeflow Pipelines prior to 2.18.0, the multi-user HTTP endpoints for uploading pipelines and pipeline versions skip SubjectAccessReview when the target namespace is empty and REQUIRE_NAMESPACE_FOR_PIPELINES defaults to false. A low-privilege tenant can create shared pipelines or inject attacker-controlled versions into existing shared pipelines without the required write permission. If the API server is directly reachable without an authenticating proxy, an unauthenticated caller can exploit the same bypass.
- CVE-2026-119757Critical
BTCPay Server before 2.4.2, including 2.4.2 release candidates, contains an information disclosure vulnerability that allows unauthenticated remote attackers to retrieve .macaroon credential files for an LND node. The exposed macaroon can be used to gain full control of the LND node, including moving funds, resulting in theft of funds.
- CVE-2026-111494Critical
The MatchPoint Android app incorrectly validates TLS certificates due to a TrustManager that accepts any certificate and a permissive hostname validator. The app also allows unencrypted HTTP traffic, enabling an attacker who intercepts traffic to read and modify communications, including credentials and personal data.
- CVE-2026-111490Critical
An insecure direct object reference (IDOR) vulnerability in the MatchPoint API relies on the `actingasuser` HTTP header without verifying the requester's authorization for the specified user. Manipulation of sequential identifiers allows access to personal, banking, and financial data, private messages, and physical-access QR codes, as well as modification of third-party accounts, password changes, impersonation, and virtual balance transfers.
- CVE-2026-111489Critical
A static credential embedded in the MatchPoint mobile app has been reported to return the 'autorizado' token. The report states that this token grants unauthenticated access to API services.
- CVE-2026-85076Critical
Prior to 0.9.124, an authenticated non-admin with run_events, create_events, or edit_events privilege in Cronicle can supply undeclared keys in event params through api_create_event, api_update_event, or api_run_event. A key colliding with a security-sensitive environment variable can override the plugin execution context, potentially causing privilege escalation, arbitrary code execution, data access, or service disruption.
- CVE-2026-48705Critical
Prior to 1.6.1, MONAI's PydicomReader._get_affine() trusts non-finite values in DICOM PixelSpacing, ImagePositionPatient, and ImageOrientationPatient fields and composes them into an affine matrix without validation. An unauthenticated attacker who can upload a crafted DICOM to a default MONAILabel deployment can propagate NaN or infinity values, causing inference failures, persistent datastore poisoning, or geometrically corrupted results.
- CVE-2026-46350Critical
Prior to 0.52.0, dcmjs's DecimalString and IntegerString implementations in src/ValueRepresentation.js sanitize text with a permissive regular expression and pass the result to JavaScript's Number constructor without validating finiteness or DICOM rules. Scientific notation overflow in a DS or IS field can produce Infinity or NaN, and IntegerString accepts exponent notation and values outside the signed 32-bit IS range. Applications trusting these values can propagate invalid numbers into geometry, windowing, dose scaling, and volume reconstruction.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

