Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-j2q8-xx3q-8fqh

Apache Storm's Improper Handling of TLS Client Authentication Failure Leads to Anonymous Principal Assignment

CVSS 6.5 MediumEPSS 0.0029 · 21st percentile

Published by the GitHub Advisory Database at 27 Apr 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.storm:storm-clientMaven<2.8.72.8.7
Identifiers
GHSA-j2q8-xx3q-8fqh · CVE-2026-41081
Weakness (CWE)
CWE-287
Tags
Published
27 Apr 2026
Updated
5 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Storm storm-client versions up to 2.8.7 are affected. When TLS is enabled without requiring client certificates (the default), a client that presents no certificate or fails certificate verification is silently assigned the principal CN=ANONYMOUS instead of being rejected. An unauthenticated client can then reach Storm services, and may bypass authorization if the configured authorizer does not explicitly deny that principal. Upgrade to 2.8.7, or enable mandatory client certificate authentication and explicitly deny CN=ANONYMOUS in authorization rules.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0029, the 21st percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.