Apache Storm Client: Anonymous principal assigned on TLS client certificate verification failure
Improper Handling of TLS Client Authentication Failure Leading to Anonymous Principal Assignment in Apache Storm Versions Affected: up to 2.8.7 Description: When TLS transport is enabled in Apache Storm without requiring client certificate authentication (the default configuration), the TlsTransportPlugin assigns a fallback principal (CN=ANONYMOUS) if no client certificate is presented or if certificate verification fails. The underlying SSLPeerUnverifiedException is caught and suppressed rather than rejecting the connection. This fail-open behavior means an unauthenticated client can establish a TLS connection and receive a valid principal identity. If the configured authorizer (e.g., SimpleACLAuthorizer) does not explicitly deny access to CN=ANONYMOUS, this may result in unauthorized access to Storm services. The condition is logged at debug level only, reducing visibility in production. Impact: Unauthenticated clients may be assigned a principal identity, potentially bypassing authorization in permissive or misconfigured environments. Mitigation: Users should upgrade to 2.8.7 in which TLS authentication failures are handled in a fail-closed manner. Users who cannot upgrade immediately should: - Enable mandatory client certificate authentication (nimbus.thrift.tls.client.auth.required: true) - Ensure authorization rules explicitly deny access to CN=ANONYMOUS - Review all ACL configurations for implicit default-allow behavior
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-41081
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 06:07 UTC · Revision 1
Source evidence
Apache Storm Client: Anonymous principal assigned on TLS client certificate verification failure
core-osv · Original sourcePublished 27 Apr 2026, 13:10 UTC
Improper Handling of TLS Client Authentication Failure Leading to Anonymous Principal Assignment in Apache Storm Versions Affected: up to 2.8.7 Description: When TLS transport is enabled in Apache Storm without requiring client certificate authentication (the default configuration), the TlsTransportPlugin assigns a fallback principal (CN=ANONYMOUS) if no client certificate is presented or if certificate verification fails. The underlying SSLPeerUnverifiedException is caught and suppressed rather than rejecting the connection. This fail-open behavior means an unauthenticated client can establish a TLS connection and receive a valid principal identity. If the configured authorizer (e.g., SimpleACLAuthorizer) does not explicitly deny access to CN=ANONYMOUS, this may result in unauthorized access to Storm services. The condition is logged at debug level only, reducing visibility in production. Impact: Unauthenticated clients may be assigned a principal identity, potentially bypassing authorization in permissive or misconfigured environments. Mitigation: Users should upgrade to 2.8.7 in which TLS authentication failures are handled in a fail-closed manner. Users who cannot upgrade immediately should: - Enable mandatory client certificate authentication (nimbus.thrift.tls.client.auth.required: true) - Ensure authorization rules explicitly deny access to CN=ANONYMOUS - Review all ACL configurations for implicit default-allow behavior
osv:CVE-2026-41081
Complete source record
{
"id": "90937b263168d5e54e32ccce633350919fb8da1c47fac68a81f0934201292197",
"url": "https://osv.dev/vulnerability/CVE-2026-41081",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Apache Storm Client: Anonymous principal assigned on TLS client certificate verification failure",
"summary": "Improper Handling of TLS Client Authentication Failure Leading to Anonymous Principal Assignment in Apache Storm Versions Affected: up to 2.8.7 Description: When TLS transport is enabled in Apache Storm without requiring client certificate authentication (the default configuration), the TlsTransportPlugin assigns a fallback principal (CN=ANONYMOUS) if no client certificate is presented or if certificate verification fails. The underlying SSLPeerUnverifiedException is caught and suppressed rather than rejecting the connection. This fail-open behavior means an unauthenticated client can establish a TLS connection and receive a valid principal identity. If the configured authorizer (e.g., SimpleACLAuthorizer) does not explicitly deny access to CN=ANONYMOUS, this may result in unauthorized access to Storm services. The condition is logged at debug level only, reducing visibility in production. Impact: Unauthenticated clients may be assigned a principal identity, potentially bypassing authorization in permissive or misconfigured environments. Mitigation: Users should upgrade to 2.8.7 in which TLS authentication failures are handled in a fail-closed manner. Users who cannot upgrade immediately should: - Enable mandatory client certificate authentication (nimbus.thrift.tls.client.auth.required: true) - Ensure authorization rules explicitly deny access to CN=ANONYMOUS - Review all ACL configurations for implicit default-allow behavior",
"evidence": "osv:CVE-2026-41081",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-41081",
"aliases": [
"CVE-2026-41081",
"GHSA-j2q8-xx3q-8fqh"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/apache/storm",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "db9cce52989123da301e401f4b7561848dd625af"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:apache:storm:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "2.8.7"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"v2.8.5",
"v2.8.4",
"v2.8.3",
"v2.8.2",
"v2.8.1",
"v2.8.0",
"v2.7.1",
"v2.7.0",
"v2.6.4",
"v2.6.3",
"v2.6.1",
"v2.5.0",
"v2.0.0",
"PRE_SECURITY_MERGE",
"v0.9.3-rc1",
"v0.9.2-incubating",
"v0.9.1-incubating",
"0.9.0.1",
"0.9.0",
"0.9.0-rc3",
"0.9.0-rc2",
"0.9.0-rc1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-41081.json"
}
}
],
"modified": "2026-10-28T02:30:42.904792720Z",
"provider": "osv",
"references": [
"https://repo.maven.apache.org/maven2/",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41081.json",
"https://lists.apache.org/thread/plxx5l29dvplk5rwzdcq53rdfl6v4gs8",
"https://nvd.nist.gov/vuln/detail/CVE-2026-41081"
],
"provider_metadata": {
"cwe_ids": [
"CWE-287"
],
"cna_assigner": "apache",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "2.8.7"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/41xxx/CVE-2026-41081.json"
}
},
"related_cves": [
{
"value": "CVE-2026-41081",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 510969,
"published_at": "2026-04-27T13:10:45.886+00:00"
}