CVE-2026-56275: Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows

Q: How do I fix CVE-2026-56275?

flowise: upgrade to 3.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-56275 being exploited?

CVE-2026-56275 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-56275 affect?

CVE-2026-56275 affects flowise. Severity is high (CVSS 7.1). Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP r

Q: How urgent is CVE-2026-56275?

Priority 36/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-56275 is a high-severity flaw (CVSS 7.1) affecting flowise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP requests to internal network addresses, access cloud metadata, and enumerate internal services by exploiting the missing secureFetch verification in httpSecurity.ts.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 76%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-06-23
Last modified	2026-10-25

Publisher (CNA): VulnCheck · Vendor: flowiseai

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-23 13:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

flowiseai flowise UPGRADE

Affected: < 3.1.0

Fixed in: 3.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy flowise || rpm -q flowise || flowise --version

2. UPGRADE to 3.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade flowise

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade flowise

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-56275?

flowise: upgrade to 3.1.0. Exact commands for each OS are on this page.

Is CVE-2026-56275 being exploited?

CVE-2026-56275 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-56275 affect?

CVE-2026-56275 affects flowise. Severity is high (CVSS 7.1). Flowise before 3.1.0 contains a server-side request forgery vulnerability in the Execute Flow node that allows attackers to bypass security validation by providing intranet addresses through the base URL field. Attackers can initiate HTTP r

How urgent is CVE-2026-56275?

Priority 36/100. High severity; Public exploit reference

Related CVEs

CVE-2026-56268 HIGH 7.7 UPGRADE Flowise before 3.1.2 contains an information disclosure vulnerability in the /api/v1/chatflows/apikey/:apikey
CVE-2026-56269 MEDIUM 4.6 UPGRADE Flowise before 3.1.0 (npm package flowise, versions 3.0.13 and earlier) uses a weak hardcoded default value 'S
CVE-2026-56272 MEDIUM 4.1 UPGRADE Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the O
CVE-2026-58057 MEDIUM 5.0 UPGRADE Flowise before 3.1.3 validates Custom MCP stdio environment variables against a denylist using a case-sensitiv
CVE-2026-56271 CRITICAL 9.8 UPGRADE Flowise before 3.1.0 (affected versions 3.0.13 and earlier) uses weak hardcoded default JWT secrets ('auth_tok

References

← Back to latest CVEs