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

New CVE Detected

CVE-2026-10564 – SSRF / Cloud Metadata Credential Theft – IBM Langflow OSS 1.0.0–1.9.6

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

Summary

CVE-2026-10564 is a high-severity Server-Side Request Forgery (SSRF) vulnerability (CWE-918) affecting IBM Langflow OSS versions 1.0.0 through 1.9.6. The flaw resides in the legacy RSSReaderComponent and SearXNG components, which bypass SSRF protections introduced in version 1.9.3 by making unvalidated HTTP requests to user-controlled URLs. With a CVSS v3.1 base score of 8.2 (High), successful exploitation can expose cloud instance metadata services on AWS, Azure, and GCP, enabling IAM credential exfiltration and internal network enumeration.

Technical details

  • Root cause: The RSSReaderComponent (rss.py) and SearXNG component (searxng.py) perform unvalidated HTTP requests to attacker-supplied URLs, failing to apply the SSRF filtering logic introduced in Langflow OSS 1.9.3. The legacy code paths were not updated when the protections were added, leaving them as exploitable bypass routes.
  • Trigger conditions: The vulnerability can be reached directly through the affected components’ API endpoints. Additionally, the SearXNG component’s tool_mode=True exposure allows the flaw to be triggered via prompt injection in agentic AI workflows — without requiring direct user credentials on the path from prompt to component invocation.
  • Attack vector: Network-accessible; no user interaction required. The formal CVSS v3.1 vector scores Privileges Required as None (PR:N), reflecting the prompt-injection trigger path. Direct component invocation may require a valid user session.
  • Impact: An attacker can force the Langflow server to issue HTTP requests to internal resources, including cloud Instance Metadata Service (IMDS) endpoints (e.g., http://169.254.169.254/). This enables exfiltration of IAM role credentials on AWS, Azure, and GCP, and allows enumeration of services on internal networks that would otherwise be unreachable from the internet.

Affected software

  • IBM Langflow OSS versions 1.0.0 through 1.9.6 (inclusive)

Severity

  • CVSS v3.1 Base Score: 8.2 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
  • CWE: CWE-918 – Server-Side Request Forgery (SSRF)

Mitigation and recommended actions

  • Immediate action – upgrade: Apply the vendor-released fix by upgrading to Langflow OSS version 1.10.0 or later, available via PyPI (pip install --upgrade langflow). Version 1.10.0 addresses the unvalidated URL handling in both affected components.
  • No workarounds available: IBM has confirmed that no workarounds are available for this vulnerability. Upgrade is the only remediation.
  • Network-level defence (interim): If immediate upgrading is not feasible, restrict inbound access to Langflow API endpoints at the network perimeter, and block outbound HTTP traffic from Langflow server instances to cloud IMDS IP ranges (e.g., 169.254.169.254/32) via host-based firewall rules or cloud security group policies.
  • Agentic pipeline review: Audit any deployed Langflow agentic workflows that use the RSSReaderComponent or SearXNG component with tool_mode=True, and remove or disable them until the upgrade is applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge