Skip to main content
VulnerabilityPublished Updated

CVE-2026-44613: Apache Zeppelin · Cross-Site Request Forgery (CSRF) Vulnerability

Affects zeppelinSource GCVE Database

0
Compare
Authoritative record:CVE-2026-44613· Medium 6.1

Not known to be exploited · CVSS 6.1 Medium : upgrade to 0.12.1 when convenient.

Data as of 29 Oct 2026, 07:15 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.12.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jul 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 29 Oct 2026.

What to do

Upgrade org.apache.zeppelin/zeppelin to 0.12.1.

Affected software

ProductAffectedFixed in
Mavenorg.apache.zeppelin/zeppelinpkg:maven/org.apache.zeppelin/zeppelinOther threatsAffected
  • >=0.6.0 <0.12.1
Fixed in
  • 0.12.1

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 Apache Zeppelin to version 0.12.1, which contains the official fix for this CSRF vulnerability. No other mitigations are indicated or required beyond applying this update.

Description

Apache Zeppelin versions 0.6.0 through 0.12.0 have a Cross-Site Request Forgery (CSRF) vulnerability due to a permissive default CORS configuration that allows cross-origin state-changing requests and accepts text/plain request bodies. This enables an attacker to trick an authenticated user into performing unintended actions via REST and WebSocket endpoints. The issue is fixed in version 0.12.1.

References

Community reviews

Loading reviews…