CVE-2026-41272Public exploitNetwork attack vector

Authenticated SSRF via flawed request wrappers

Published Apr 23, 2026 · Updated Apr 23, 2026

SSRF in Flowise before 3.1.0 allows remote authenticated users to access internal services through crafted workflow requests. The secureAxiosRequest and secureFetch wrappers in packages/components/src/httpSecurity.ts skip deny-list checks when HTTP_DENY_LIST is unset and separately resolve a hostname before the HTTP client resolves it again. Low-privileged Flowise access and a node that invokes either wrapper are required; successful exploitation reads internal service responses or issues state-changing GET requests.

CVSS severity7.1
High
EPSS probability0.26%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

SSRF in Flowise before 3.1.0 allows remote authenticated users to access internal services through crafted workflow requests. The secureAxiosRequest and secureFetch wrappers in packages/components/src/httpSecurity.ts skip deny-list checks when HTTP_DENY_LIST is unset and separately resolve a hostname before the HTTP client resolves it again. Low-privileged Flowise access and a node that invokes either wrapper are required; successful exploitation reads internal service responses or issues state-changing GET requests.

The record

CVE
CVE-2026-41272
Published
Apr 23, 2026
Updated
Apr 23, 2026
Vendor
FlowiseAI
Product
Flowise
Classifications
CWE-918, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 23, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

FlowiseAI · Flowiseversion=< 3.1.0
FlowiseAI · flowise-componentsversion=< 3.1.0

Published CVSS scores

7.1GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo