CVE-2026-41279 affects Flowise prior to version 3.1.0. The vulnerability is in the whitelisted, unauthenticated text-to-speech generation endpoint at POST /api/v1/text-to-speech/generate. This endpoint accepts a credentialId directly in the request body. When the endpoint is invoked without a chatflowId, Flowise uses the supplied credentialId to locate and decrypt a stored credential, such as an OpenAI or ElevenLabs API key, and then uses that credential to perform text-to-speech generation. The flaw is an authorization failure / user-controlled key reference issue in which an unauthenticated caller can cause the application to operate on a credential selected by identifier rather than enforcing proper ownership or access controls.
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.
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.