Loading vulnerability…
CVE-2026-44613 is a cross-site request forgery vulnerability in Apache Zeppelin affecting versions 0.6.0 through 0.12.0. The flaw arose from Zeppelin’s default CORS behavior permitting cross-origin state-changing requests and from affected endpoints accepting text/plain request bodies, which enabled requests to avoid normal browser preflight protections. As a result, a remote attacker could induce a victim with an active authenticated Zeppelin session to load a malicious webpage and then issue forged requests against Zeppelin REST and WebSocket endpoints in the victim’s browser context. The vulnerability allowed unauthorized actions to be performed without requiring the attacker to know the victim’s credentials.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small single-script exploit repository centered on cve-2026-44613.py. The Python script starts a local HTTP server on 127.0.0.1:8000 and serves a malicious HTML/JavaScript page designed to exploit CVE-2026-44613 in Apache Zeppelin 0.6.0–0.12.0. The browser-side payload uses fetch() with credentials included to send cross-origin GET, POST, and PUT requests to a Zeppelin instance at http://127.0.0.1:8080 by default. Its capabilities go beyond simple detection: it performs reconnaissance against multiple Zeppelin API endpoints, creates notebooks, injects paragraphs including a shell-interpreter example, attempts interpreter setting creation and restart, and probes credential/configuration/repository endpoints. The repository contains only four files: license, gitignore, README, and the exploit script. README is mostly generic usage/disclaimer text and does not add operational logic. Overall, this is a real browser-based CSRF PoC for Zeppelin with visible side effects and moderate operational capability, but it is not framework-based and does not include a customizable post-exploitation agent.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.