Loading vulnerability…
CVE-2026-41273 is an authentication bypass vulnerability in Flowise, a drag-and-drop interface for building customized large language model workflows. Versions prior to 3.1.0 expose a public chatflow configuration endpoint that can disclose internal workflow data for public chatflows, including OAuth credential identifiers. An unauthenticated remote attacker can query this endpoint, extract those identifiers, and then use them in the OAuth token refresh flow to obtain valid OAuth 2.0 access tokens without being authenticated. The issue stems from missing authentication on a critical configuration endpoint and insufficient authorization checks around use of stored OAuth credentials during token refresh operations.
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.