Read the docs
TI-2026-29300 Aliases CVE-2026-40557GHSA-82fm-wpc2-5pmp

Improper certificate validation in Apache Storm Prometheus Reporter

Priority LOW 21CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Spoofing
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub. Impact type from CWE-295.

Summary

Improper Certificate Validation via Global SSL Context Downgrade in Apache Storm Prometheus Reporter Versions Affected: from 2.6.3 to 2.8.6 Description:  In production deployments where an administrator enables storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation (by default it is disabled) intending to affect only the Prometheus reporter, the undocumented global side effect creates an attack surface across every TLS-protected communication channel in the Storm daemon. The PrometheusPreparableReporter class implements an INSECURE_TRUST_MANAGER that accepts all SSL certificates without validation, with empty checkClientTrusted and checkServerTrusted methods. Most critically, when the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation configuration option is enabled (default = disabled) for HTTPS Prometheus PushGateway connections, the INSECURE_CONNECTION_FACTORY calls SSLContext.setDefault(sslContext), which globally replaces the JVM's default SSL context rather than applying the insecure context only to the Prometheus connection. This payload flows through storm.yaml configuration → PrometheusPreparableReporter.prepare() → INSECURE_CONNECTION_FACTORY → SSLContext.setDefault(), resulting in a JVM-wide TLS security downgrade. All subsequent HTTPS connections in the process - including ZooKeeper, Thrift, Netty, and UI connections - silently trust all certificates, including self-signed, expired, and attacker-generated ones, enabling man-in-the-middle interception of cluster state, topology submissions, tuple data, and administrative credentials. Mitigation: 2.x users should upgrade to 2.8.7 if the Prometheus Metrics Reporter is used. Prometheus Metrics Reporter Users who cannot upgrade immediately should remove the storm.daemon.metrics.reporter.plugin.prometheus.skip_tls_validation: true setting from their storm.yaml configuration and instead configure a proper truststore containing the PushGateway's certificate.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00193 9th percentileScored 2026-11-07
Fix Fixed Apache Storm Prometheus Reporter (Apache Software Foundation): 2.8.7org.apache.storm:storm-metrics-prometheus (Maven): 2.8.7

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Storm Prometheus Reporter2.6.3 to before 2.8.72.8.7Patch availableCNA
—org.apache.storm:storm-metrics-prometheus (Maven)2.6.3 to before 2.8.72.8.7Patch availableGHSA-82fm-wpc2-5pmp
  • Apache Storm Prometheus Reporter VendorApache Affected 2.6.3 to before 2.8.7 Fixed in 2.8.7 Patch available CNA
  • org.apache.storm:storm-metrics-prometheus (Maven) Vendor— Affected 2.6.3 to before 2.8.7 Fixed in 2.8.7 Patch available GHSA-82fm-wpc2-5pmp

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:storm_prometheus_reporter:*:*:*:*:*:*:*:*2.6.3 to before 2.8.7VulnerableApache
  • cpe:2.3:a:apache:storm_prometheus_reporter:*:*:*:*:*:*:*:* Versions 2.6.3 to before 2.8.7 Vulnerable ·Apache

Remediation

  • Fix · CNA Apache Storm Prometheus Reporter (Apache Software Foundation) Fixed in 2.8.7
  • Fix · GHSA-82fm-wpc2-5pmp org.apache.storm:storm-metrics-prometheus (Maven) Fixed in 2.8.7 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-40557
  2. 2026-10-03 Alias added: GHSA-82fm-wpc2-5pmp

References

Sources