CVE-2025-68477VulnerabilityPublished 19 Dec 2025

CVE-2025-68477: langflow · Server-Side Request Forgery (SSRF)

Affects langflowSource CVE Database V5

Not known to be exploited · CVSS 7.7 High : upgrade to 1.7.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 6.3% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.7.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade langflow-ai/langflow to 1.7.0.

Affected software

Product	Affected	Fixed in
GitHublangflow-ai/langflow`pkg:github/langflow-ai/langflow`Other threats	Affected <1.7.0	Fixed in 1.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should take the following specific mitigation steps: 1) Immediately upgrade langflow installations to version 1.7.0 or later, which contains the patch that properly restricts SSRF vectors. 2) Audit and restrict API key distribution and usage to minimize the risk of unauthorized access to flow execution endpoints. 3) Implement network segmentation and firewall rules to limit the server's ability to access sensitive internal IP ranges and cloud metadata endpoints, adding a defense-in-depth layer. 4) Monitor API usage logs for unusual or unexpected requests targeting internal IP ranges or metadata endpoints. 5) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) that can detect and block SSRF patterns. 6) Conduct internal security assessments and penetration tests focusing on SSRF and internal resource access via AI workflow tools. 7) Educate developers and administrators about the risks of SSRF in AI automation platforms and enforce secure coding and configuration practices. These steps go beyond generic advice by focusing on controlling API key access, network-level restrictions, and active monitoring tailored to the langflow environment.

Description

Langflow is a tool for building and deploying AI-powered agents and workflows. Prior to version 1.7.0, Langflow provides an API Request component that can issue arbitrary HTTP requests within a flow. This component takes a user-supplied URL, performs only normalization and basic format checks, and then sends the request using a server-side httpx client. It does not block private IP ranges (127[.]0[.]0[.]1, the 10/172/192 ranges) or cloud metadata endpoints (169[.]254[.]169[.]254), and it returns the response body as the result. Because the flow execution endpoints (/api/v1/run, /api/v1/run/advanced) can be invoked with just an API key, if an attacker can control the API Request URL in a flow, non-blind SSRF is possible—accessing internal resources from the server’s network context. This enables requests to, and collection of responses from, internal administrative endpoints, metadata services, and internal databases/services, leading to information disclosure and providing a foothold for further attacks. Version 1.7.0 contains a patch for this issue.

Impact

For European organizations, the impact of CVE-2025-68477 can be significant, especially for those leveraging langflow to automate AI-powered workflows that interact with internal systems. Exploitation could lead to unauthorized disclosure of sensitive internal data, including cloud metadata that may contain credentials or tokens for further access. This can compromise confidentiality and potentially enable attackers to pivot within the network, access internal administrative endpoints, or exfiltrate data. Given the increasing adoption of AI tools and cloud services in Europe, organizations running langflow on cloud infrastructure or within private networks are at risk of internal network reconnaissance and data leakage. The vulnerability could also undermine trust in AI automation platforms and lead to regulatory compliance issues under GDPR if personal or sensitive data is exposed. The absence of known exploits reduces immediate risk but does not eliminate the threat, as attackers may develop exploits rapidly once the vulnerability is public. The requirement of an API key limits exposure but does not eliminate risk, especially if API keys are leaked or insufficiently protected.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/langflow-ai/langflow/security/advisories/GHSA-5993-7p27-66g5 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Dec 2025, 17:11 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats