SSRF via HTTP Redirect Following in Langflow API Request Component
IBM Langflow OSS 1.0.0 through 1.9.3 contains a Server-Side Request Forgery (SSRF) protection bypass vulnerability in the API Request component. An authenticated attacker with low-level privileges (flow author role) can bypass SSRF protections by enabling the follow_redirects parameter and supplying a public URL that redirects to internal/localhost addresses. The vulnerability exists because the application validates only the initial URL but does not re-validate redirect destinations. This allows attackers to access internal HTTP services, localhost endpoints, cloud metadata services, and private network resources that should be unreachable when SSRF protection is enabled. Successful exploitation can lead to disclosure of sensitive information including credentials, tokens, internal API responses, and administrative panel data.
- Published
- Jun 30, 2026
- Updated
- Jul 2, 2026
- EPSS
- 0.3% · 22th percentile
- CWE
- CWE-918
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · ibm
- 8.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| langflow | langflow | cpe:2.3:a:langflow:langflow |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- langflow langflow1.0.0 and later · up to 1.9.3 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Langflow OSS
- 1.0.0 and later · up to and including 1.9.3affected · semver
Same product
langflow: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-3248Langflow < 1.3.0 Unauthenticated RCE via /api/v1/validate/codeKEV99Now
- CVE-2025-34291Langflow <= 1.6.9 CORS Misconfiguration to Token Hijack & RCEKEV95Now
- CVE-2026-0770Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote Code Execution VulnerabilityKEV88Now
- CVE-2026-9198Unauthenticated Remote Code Execution via Auto-Login Bypass and Code ValidationKEV78This week
- CVE-2026-33017Langflow has Unauthenticated Remote Code Execution via Public Flow Build EndpointKEV74This week
- CVE-2026-55255Langflow: IDOR Vulnerability in `/api/v1/responses` Endpoint Allows Authenticated Attackers to Access Another User's FlowKEV63This week
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-8121372 days apartLangflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetches34Monitor
- CVE-2026-105640 days apartSSRF Vulnerability in Langflow OSS Legacy Components Bypasses Protection32Monitor
- CVE-2026-1930466 days apartLangflow is vulnerable to Server-Side Request Forgery due to missing or bypassable URL validation in multiple components30Monitor
- CVE-2026-1930566 days apartLangflow is vulnerable to Server-Side Request Forgery due to missing or bypassable URL validation in multiple components30Monitor
- CVE-2026-8126572 days apartLangflow is vulnerable to server-side request forgery due to missing egress validation on server-side URL fetches30Monitor
- CVE-2026-908136 days apartLangflow OSS is affected by server-side request forgery in provider validation and API request functionality28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2026-105618 days apartUnauthenticated Remote Code Execution in Langflow OSS PythonREPLComponent via Builtins Injection40Plan
- CVE-2026-76648 days apartUnauthenticated Flow Execution via Webhook Endpoint in Langflow OSS39Monitor
- CVE-2026-105600 days apartUnauthenticated Access to Private Flow Build Events and Cancellation in Langflow OSS36Monitor
- CVE-2026-778719 days apartUnauthenticated Session History Access via Public Flow Execution32Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.