Loading vulnerability…
CVE-2026-65595 is a privilege escalation vulnerability in n8n affecting versions before 2.30.1 and before 2.29.8 on the affected maintenance branch. The flaw is caused by incorrect privilege handling in the Token Exchange module: JWTs issued through Token Exchange are assigned all Public API key scopes regardless of the acting user's actual role. On deployments where both Token Exchange and the Public API are enabled, a low-privileged user who can obtain a valid external JWT trusted by a configured issuer can exchange it for an access token that is over-scoped and accepted for administrator-only Public API operations. Exposed actions include administrative user management functions such as user creation, user deletion, and role escalation. In configurations that also permit installation of unverified Community Packages, the privilege escalation can be chained into remote code execution.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.