User-privileged actions via permissive cross-origin requests
Published Jul 30, 2026 · Updated Jul 30, 2026
CSRF in Apache Zeppelin 0.6.0 through 0.12.0 allows remote attackers to perform actions through REST and WebSocket endpoints. REST and WebSocket request handling uses a wildcard CORS origin default and accepts text/plain bodies for state-changing requests, so browsers send authenticated cross-origin actions. Exploitation requires an authenticated user to visit an attacker-controlled site; resulting actions carry that user’s Zeppelin privileges.
Summary
What happened
CSRF in Apache Zeppelin 0.6.0 through 0.12.0 allows remote attackers to perform actions through REST and WebSocket endpoints. REST and WebSocket request handling uses a wildcard CORS origin default and accepts text/plain bodies for state-changing requests, so browsers send authenticated cross-origin actions. Exploitation requires an authenticated user to visit an attacker-controlled site; resulting actions carry that user’s Zeppelin privileges.
The record
- CVE
- CVE-2026-44613
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Zeppelin
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.6.0 <0.12.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo