Skip to main content
VulnerabilityPublished

CVE-2026-124496: The DRPC HTTP endpoint lets an authenticated client act as another user without applying the

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-124496· High

Not known to be exploited : upgrade to 3.2.0 soon.

Data as of 11 Nov 2026, 16:48 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.2.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade Apache Storm and org.apache.storm/storm-server to 3.2.0.

Affected software

ProductAffectedFixed in
Apache Stormorg.apache.storm:storm-serverAffected
  • >=3.0.0 <3.2.0
Fixed in
  • 3.2.0
Mavenorg.apache.storm/storm-serverpkg:maven/org.apache.storm/storm-serverOther threatsAffected
  • >=3.0.0 <3.2.0
Fixed in
  • 3.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to version 3.2.0, which contains the fix for this vulnerability. No other mitigation or temporary workaround is indicated in the provided data.

Description

CVE-2026-124496 is a vulnerability in the DRPC HTTP endpoint that allows an authenticated client to act as another user without proper authorization checks. This flaw bypasses the configured impersonation authorizer, enabling execution of DRPC functions restricted to other users. The issue is fixed in version 3.2.0.

References

Community reviews

Loading reviews…