dbcve.org
LangflowApplication

CVE-2026-10546

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to after 1.9.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Langflow OSS 1.0.0 through 1.9.3 contains a Server-Side Request Forgery (SSRF) vulnerability in the URL component ( src/lfx/src/lfx/components/data_source/url.py ) due to a Time-of-Check/Time-of-Use (TOCTOU) race condition that can be exploited via DNS rebinding.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Langflow OSS versions 1.0.0 through 1.9.3 contains a Server-Side Request Forgery (SSRF) vulnerability in the URL component (src/lfx/src/lfx/components/data_source/url.py) stemming from a Time-of-Check/Time-of-Use (TOCTOU) race condition exploitable via DNS rebinding attacks.

MitigationUpgrade to a version beyond 1.9.3 when available, and implement DNS rebinding protections (e.g., DNS pinphg, allowlist validation, and resolving hostname immediately before making the request) in the URL handling code.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LangflowApplication
Affected:>= 1.0.0, <= 1.9.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Langflow version
    Run 'pip show langflow' or check package.json/version file in your Langflow installation directory to obtain the exact version number
    Affected if Version is >= 1.0.0 and <= 1.9.3
  2. Locate the vulnerable URL component
    Check if the file src/lfx/src/lfx/components/data_source/url.py exists in your Langflow installation. This is the vulnerable component.
    Affected if The file exists and your version is in the affected range
  3. Determine if URL data source is in use
    Review your Langflow flows, agents, or configurations to see if any component is configured to fetch data from external URLs using the URL component
    Affected if Flows or agents are making HTTP requests to arbitrary URLs through Langflow
  4. Inspect HTTP request handling
    Examine network logs or Langflow access/debug logs for outbound HTTP/HTTPS requests originating from the Langflow service, particularly to user-supplied URLs
    Affected if The application is processing URLs from untrusted input and making outbound requests

You are affected if your Langflow version is between 1.0.0 and 1.9.3 inclusive and your flows or agents use the URL component to fetch data from external sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.9.3
Interim mitigation

Upgrade to a version beyond 1.9.3 when available, and implement DNS rebinding protections (e.g., DNS pinphg, allowlist validation, and resolving hostname immediately before making the request) in the URL handling code.

Recommended fix Moderate confidence

Upgrade to the latest Langflow release (version > 1.9.3) that includes the SSRF fix for the URL component vulnerability.

  1. 1. Identify the current Langflow version installed in your environment using 'pip show langflow' or checking your dependency files.
  2. 2. Review the Langflow release notes and GitHub repository for versions beyond 1.9.3 to identify the appropriate fixed release.
  3. 3. Upgrade Langflow by running: pip install --upgrade langflow
  4. 4. Verify the upgrade was successful and the new version is running: pip show langflow
  5. 5. Test the URL component functionality to ensure the SSRF fix does not break legitimate use cases.
  6. 6. If using a containerized deployment, rebuild the container image with the updated Langflow version.
Caveat Review release notes for any breaking changes between 1.9.3 and the target version, particularly around URL/data source handling functionality.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Langflow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10546 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10546 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data