Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-81213 – Unauthenticated SSRF – IBM Langflow OSS 1.0.0 through 1.11.5

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-81213 is a server-side request forgery (SSRF) vulnerability in IBM Langflow OSS. Due to improper validation of user-supplied URLs, a remote, unauthenticated attacker can cause the Langflow server to issue requests to internal network resources, potentially exposing sensitive information from systems that should not be reachable externally. The flaw carries a CVSS v3.1 base score of 8.6 (High).

Technical details

  • Root cause: Langflow does not properly validate or restrict URLs supplied by users before the server uses them to make outbound HTTP(S) requests, allowing egress to arbitrary destinations, including internal-only hosts and cloud metadata endpoints.
  • Trigger conditions: An attacker submits a crafted request containing a URL pointing at an internal address (e.g., RFC 1918 ranges or cloud instance metadata services); no authentication or user interaction is required to trigger the request.
  • Attack vector: Network-based (AV:N), low attack complexity, no privileges required, no user interaction — exploitable directly over the network against an exposed Langflow instance.
  • Impact: The server-side fetch can be abused to enumerate or read data from internal-only services and metadata endpoints reachable from the Langflow host, resulting in high confidentiality impact with a changed scope (the affected component can impact resources beyond its own security scope).

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.11.5

Severity

  • CVSS v3.1 Base Score: 8.6 (High)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade Langflow OSS to version 1.11.6 or later, available via PyPI.
  • If patching is not immediately possible: Restrict network access to Langflow instances so they are not reachable from untrusted networks, and place egress controls/firewalling around the host running Langflow to prevent server-side requests from reaching internal-only services or cloud metadata endpoints. No other workaround has been documented by the vendor.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge