Is CVE-2026-44613 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-44613 being exploited in the wild.

How severe is CVE-2026-44613?

Informational severity, with a CVSS score of 0, published 30 July 2026.

Which products and versions are affected?

Apache Software Foundation Zeppelin 0.6.0 through 0.12.0.

Is there a fix for CVE-2026-44613?

A patch was published on 2026-05-18: GitHub pull request merged to harden CORS and request handling Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-44613 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-44613?

Check whether you run Apache Software Foundation Zeppelin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-44613: Apache Zeppelin CSRF in REST and WebSocket endpoints

CVE-2026-44613 · Severity: info · CVSS 0 · Published 2026-07-30

Apache Zeppelin, a web-based notebook for data analytics and visualization, contains a security flaw in its default configuration. An attacker could trick a logged-in user into visiting a malicious website, which then silently performs actions in Zeppelin using the user's active session. This could allow unauthorized changes to data notebooks, system settings, or other administrative actions, potentially compromising sensitive data or system integrity.

Technologies: Apache Software Foundation Zeppelin. Vendors: Apache Software Foundation.

Quick answers

Is CVE-2026-44613 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-44613 being exploited in the wild.
How severe is CVE-2026-44613?: Informational severity, with a CVSS score of 0, published 30 July 2026.
Which products and versions are affected?: Apache Software Foundation Zeppelin 0.6.0 through 0.12.0.
Is there a fix for CVE-2026-44613?: A patch was published on 2026-05-18: GitHub pull request merged to harden CORS and request handling Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44613 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44613?: Check whether you run Apache Software Foundation Zeppelin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Cross-Site Request Forgery (CSRF) vulnerability exists in Apache Zeppelin versions 0.6.0 through 0.12.0. The root cause is a permissive default CORS configuration that allowed cross-origin state-changing requests (POST, PUT, DELETE, PATCH) and accepted 'text/plain' request bodies, which bypasses standard browser CORS preflight protections. An attacker can exploit this by luring an authenticated user to a malicious site that sends forged requests to the Zeppelin REST or WebSocket endpoints. Successful exploitation allows the attacker to perform state-changing actions with the victim's privileges. The issue is resolved in version 0.12.1 by tightening origin validation, restricting accepted Content-Types, and setting 'SameSite=Lax' for session cookies.

Affected products

Apache Zeppelin 0.6.0 through 0.12.0

Timeline

2026-05-18: patched: GitHub pull request merged to harden CORS and request handling
2026-07-30: disclosed: Public disclosure via oss-security mailing list
2026-07-30: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.