Langflow vulnerable to Server-Side Request Forgery

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2025-68477: 6.30% estimated exploitation activity in the next 30 days; percentile 93.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Vulnerability Overview 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. Vulnerable Code 1. When a flow runs, the API Request URL is set via…

Published by the source

19 Dec 2025, 22:52 UTC

Last modified by the source

7 Jul 2026, 17:56 UTC

Source last checked

26 Oct 2026, 13:36 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5993-7p27-66g5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5993-7p27-66g5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68477

Advisory: Langflow vulnerable to Server-Side Request Forgery
IDs: CVE-2025-68477, GHSA-5993-7p27-66g5
Record: https://patchnext.com/advisories/cve-2025-68477 (revision 2, source checked 26 Oct 2026, 13:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: langflow 1.7.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI langflow: affected < 1.7.1; fixed in 1.7.1

## Suggested inspection (read-only)
- `python -m pip show langflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on langflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5993-7p27-66g5 (OSV record GHSA-5993-7p27-66g5 lists affected ranges: PyPI langflow >=0 <1.7.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5993-7p27-66g5 (GitHub-reviewed advisory GHSA-5993-7p27-66g5 lists affected ranges: PyPI langflow >=0 <1.7.1)

Commands are suggestions: review each one before running it.