CVE-2026-70476 is an improper authorization vulnerability in Flowise versions before 3.1.3. Organization billing operations accept a client-supplied Stripe subscription identifier without validating that the subscription is owned by the authenticated user’s active organization. This permits a tenant to target another organization’s subscription and perform cross-tenant billing changes.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Vulnerability in Flowise that could allow unauthorized manipulation of billing and application resource management information, impacting data integrity and administrative accounting processes.
An improper authorization vulnerability in Flowise organization billing endpoints that permits an authenticated tenant to manipulate another organization's Stripe subscription by supplying its subscription ID, causing financial impact and service disruption. Fixed in Flowise 3.1.3.
An authorization flaw in Flowise billing endpoints that allows attacker-controlled Stripe subscriptionId values to be used without verifying tenant ownership, enabling unauthorized cross-tenant subscription changes and seat modifications.
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.