dbcve.org
StormApplication · Apache

CVE-2026-35337

HIGH · 8.8 CVSS v3.1 Published 2026-04-13
Fix available
A fix is available. Upgrade to 2.8.6 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Deserialization of Untrusted Data vulnerability in Apache Storm. Versions Affected: before 2.8.6. Description: When processing topology credentials submitted via the Nimbus Thrift API, Storm deserializes the base64-encoded TGT blob using ObjectInputStream.readObject() without any class filtering or validation. An authenticated user with topology submission rights could supply a crafted serialized object in the "TGT" credential field, leading to remote code execution in both the Nimbus and Worker JVMs. Mitigation: 2.x users should upgrade to 2.8.6. Users who cannot upgrade immediately should monkey-patch an ObjectInputFilter allow-list to ClientAuthUtils.deserializeKerberosTicket() restricting deserialized classes to javax.security.auth.kerberos.KerberosTicket and its known dependencies. A guide on how to do this is available in the release notes of 2.8.6. Credit: This issue was discovered by K.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Storm Nimbus deserializes base64-encoded TGT credentials via ObjectInputStream.readObject() without class filtering, allowing authenticated users with topology submission rights to inject malicious serialized objects and achieve remote code execution in Nimbus and Worker JVMs.

MitigationUpgrade to Apache Storm 2.8.6 or implement an ObjectInputFilter allow-list restricting deserialization to javax.security.auth.kerberos.KerberosTicket and its dependencies.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StormApplication
Affected:>= 2.0.0, < 2.8.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Apache Storm version
    Run 'storm version' command or check the Storm jar metadata in the installation directory
    Affected if The version is 2.0.0 or higher but lower than 2.8.6
  2. Verify Nimbus is running
    Check if the Nimbus daemon is active using 'ps aux | grep nimbus' or by checking the Storm UI for the Nimbus leader status
    Affected if Nimbus is running and serving topology submissions
  3. Confirm topology submission is enabled
    Inspect the Storm configuration (storm.yaml) for 'nimbus.authorizer' or 'nimbus.acl' settings, and verify if unauthenticated or non-privileged submissions are allowed
    Affected if Topology submission is permitted for authenticated users without strict allow-list filtering on deserialized classes
  4. Check if Kerberos/TGT authentication is configured
    Look for 'java.security.auth.login.config' in Storm worker launch parameters or check for krb5.ini/jaas.conf configuration files in the Storm environment
    Affected if Kerberos authentication is enabled, as the vulnerability exploits deserialization of TGT credentials
  5. Inspect Nimbus deserialization handling
    Review Nimbus logs for ObjectInputStream.readObject() calls involving credential handling, or examine Storm security configuration for custom deserialization filters
    Affected if No ObjectInputFilter allow-list is configured for javax.security.auth.kerberos.KerberosTicket and its dependencies

You are affected if you run Apache Storm version 2.0.0 through 2.8.5 with Nimbus enabled and topology submission permitted, especially when Kerberos authentication is configured without deserialization allow-lists.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.8.6 or later
Fixed in 2.8.6
Interim mitigation

Upgrade to Apache Storm 2.8.6 or implement an ObjectInputFilter allow-list restricting deserialization to javax.security.auth.kerberos.KerberosTicket and its dependencies.

Recommended fix High confidence

2.8.6

  1. Download Apache Storm version 2.8.6 from the official Apache Storm distribution (storm.apache.org)
  2. Stop all running Nimbus and Worker JVM processes
  3. Back up your current Storm configuration and any custom scripts
  4. Replace the existing Storm installation with version 2.8.6
  5. Restore your configuration files to the new installation
  6. Start the Nimbus daemon first, then start Worker processes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Storm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35337 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35337 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data