VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

langflow-base: vulnerability history, versions and safety

langflow-base is a package in the PyPI ecosystem. Vulert records 9 vulnerabilities for it across 8 releases, from Jan 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H1 M1 U7
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
9 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all langflow-base vulnerabilities

Vulert verdict on langflow-base 1.14.0.dev3 i

Updated on 23 Oct 2026

Good news: 1.14.0.dev3, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 9.

Package health score 71/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 1.14.0.dev3 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.14.0.dev3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.14.0.dev3 — unaffected i
  • Vulnerabilities on record 9 over 1 year · 9 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Stars 155,716 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for langflow-base, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.14.0.dev3 23 Oct 2026 none MIT — Details →
1.13.0 22 Oct 2026 none MIT — Details →
1.12.8 22 Oct 2026 none MIT — Details →
1.14.0.dev2 22 Oct 2026 none MIT — Details →
1.13.0rc4 22 Oct 2026 none MIT — Details →
1.12.8rc0 21 Oct 2026 none MIT — Details →
1.13.0rc3 21 Oct 2026 none MIT — Details →
1.14.0.dev1 21 Oct 2026 none MIT — Details →
1.12.7 21 Oct 2026 none MIT — Details →
1.12.7rc0 20 Oct 2026 none MIT — Details →
1.14.0.dev0 20 Oct 2026 none MIT — Details →
1.13.0rc2 19 Oct 2026 none MIT — Details →
1.13.0.dev47 19 Oct 2026 none MIT — Details →
1.13.0.dev46 18 Oct 2026 none MIT — Details →
1.13.0.dev45 17 Oct 2026 none MIT — Details →
1.13.0rc1 16 Oct 2026 none MIT — Details →
1.13.0.dev44 16 Oct 2026 none MIT — Details →
1.13.0.dev43 15 Oct 2026 none MIT — Details →
1.13.0.dev42 14 Oct 2026 none MIT — Details →
1.13.0rc0 13 Oct 2026 none MIT — Details →
1.12.6 13 Oct 2026 none MIT — Details →
1.13.0.dev41 13 Oct 2026 none MIT — Details →
1.12.6rc3 12 Oct 2026 none MIT — Details →
1.12.5rc2 12 Oct 2026 none MIT — Details →
1.13.0.dev40 12 Oct 2026 none MIT — Details →
1.13.0.dev39 11 Oct 2026 none MIT — Details →
1.13.0.dev38 10 Oct 2026 none MIT — Details →
1.13.0.dev37 09 Oct 2026 none MIT — Details →
1.13.0.dev36 08 Oct 2026 none MIT — Details →
1.13.0.dev35 07 Oct 2026 none MIT — Details →
1.12.5 06 Oct 2026 none MIT — Details →
1.13.0.dev34 06 Oct 2026 none MIT — Details →
1.12.5rc1 05 Oct 2026 none MIT — Details →
1.13.0.dev33 05 Oct 2026 none MIT — Details →
1.12.5rc0 05 Oct 2026 none MIT — Details →
1.13.0.dev32 04 Oct 2026 none MIT — Details →
1.13.0.dev31 03 Oct 2026 none MIT — Details →
1.13.0.dev30 02 Oct 2026 none MIT — Details →
1.13.0.dev29 01 Oct 2026 none MIT — Details →
1.13.0.dev28 30 Sep 2026 none MIT — Details →
1.12.4 29 Sep 2026 none MIT — Details →
1.13.0.dev27 29 Sep 2026 none MIT — Details →
1.12.4rc0 28 Sep 2026 none MIT — Details →
1.13.0.dev26 28 Sep 2026 none MIT — Details →
1.13.0.dev25 27 Sep 2026 none MIT — Details →
1.13.0.dev24 26 Sep 2026 none MIT — Details →
1.13.0.dev23 25 Sep 2026 none MIT — Details →
1.13.0.dev22 24 Sep 2026 none MIT — Details →
1.13.0.dev21 23 Sep 2026 none MIT — Details →
1.12.3 22 Sep 2026 none MIT — Details →
1.13.0.dev20 22 Sep 2026 none MIT — Details →
1.12.3rc0 22 Sep 2026 none MIT — Details →
1.13.0.dev19 21 Sep 2026 none MIT — Details →
1.13.0.dev18 20 Sep 2026 none MIT — Details →
1.13.0.dev17 19 Sep 2026 none MIT — Details →
1.13.0.dev16 18 Sep 2026 none MIT — Details →
1.13.0.dev15 17 Sep 2026 none MIT — Details →
1.13.0.dev14 16 Sep 2026 none MIT — Details →
1.12.2 16 Sep 2026 none MIT — Details →
1.13.0.dev13 15 Sep 2026 none MIT — Details →
1.13.0.dev12 14 Sep 2026 none MIT — Details →
1.13.0.dev11 13 Sep 2026 none MIT — Details →
1.13.0.dev10 12 Sep 2026 none MIT — Details →
1.12.2rc1 11 Sep 2026 none MIT — Details →
1.13.0.dev9 11 Sep 2026 none MIT — Details →
1.12.2rc0 11 Sep 2026 none MIT — Details →
1.13.0.dev8 10 Sep 2026 none MIT — Details →
1.13.0.dev7 09 Sep 2026 none MIT — Details →
1.12.1 08 Sep 2026 none MIT — Details →
1.13.0.dev6 08 Sep 2026 none MIT — Details →
1.13.0.dev5 07 Sep 2026 none MIT — Details →
1.13.0.dev4 06 Sep 2026 none MIT — Details →
1.13.0.dev3 05 Sep 2026 none MIT — Details →
1.13.0.dev2 04 Sep 2026 none MIT — Details →
1.13.0.dev1 03 Sep 2026 none MIT — Details →
1.13.0.dev0 02 Sep 2026 none MIT — Details →
1.12.0 01 Sep 2026 none MIT — Details →
1.12.0rc4 01 Sep 2026 none MIT — Details →
1.12.0.dev45 01 Sep 2026 none MIT — Details →
0.11.6 01 Sep 2026 H1 M1 MIT Yes Details →
1.12.0.dev44 31 Aug 2026 none MIT — Details →
1.12.0.dev43 30 Aug 2026 none MIT — Details →
1.12.0rc3 29 Aug 2026 none MIT — Details →
1.12.0.dev42 29 Aug 2026 none MIT — Details →
1.12.0.dev41 28 Aug 2026 none MIT — Details →
1.12.0.dev40 27 Aug 2026 none MIT — Details →
1.12.0.dev39 26 Aug 2026 none MIT — Details →
1.12.0rc2 25 Aug 2026 none MIT — Details →
0.11.5 25 Aug 2026 H1 M1 MIT Yes Details →
1.12.0rc1 25 Aug 2026 none MIT — Details →
1.12.0rc0 25 Aug 2026 none MIT — Details →
1.12.0.dev38 25 Aug 2026 none MIT — Details →
1.12.0.dev37 24 Aug 2026 none MIT — Details →
1.12.0.dev36 23 Aug 2026 none MIT — Details →
1.12.0.dev35 22 Aug 2026 none MIT — Details →
1.12.0.dev34 21 Aug 2026 none MIT — Details →
1.12.0.dev33 20 Aug 2026 none MIT — Details →
1.12.0.dev32 19 Aug 2026 none MIT — Details →
0.11.4 18 Aug 2026 H1 M1 MIT Yes Details →
1.12.0.dev31 18 Aug 2026 none MIT — Details →
0.11.4rc3 17 Aug 2026 H1 M1 — Yes Details →
1.12.0.dev30 17 Aug 2026 none — — Details →
1.12.0.dev29 16 Aug 2026 none — — Details →
1.12.0.dev28 15 Aug 2026 none — — Details →
1.12.0.dev27 15 Aug 2026 none — — Details →
0.11.4rc2 14 Aug 2026 H1 M1 — Yes Details →
1.12.0.dev26 14 Aug 2026 none — — Details →
1.12.0.dev25 13 Aug 2026 none — — Details →
1.12.0.dev24 12 Aug 2026 none — — Details →
0.11.3 11 Aug 2026 H1 M1 — Yes Details →
1.12.0.dev23 11 Aug 2026 none — — Details →
0.11.3rc1 10 Aug 2026 H1 M1 — Yes Details →
1.12.0.dev22 10 Aug 2026 none — — Details →
1.12.0.dev21 09 Aug 2026 none — — Details →
0.11.3rc0 08 Aug 2026 H1 M1 — Yes Details →
1.12.0.dev20 08 Aug 2026 none — — Details →
1.12.0.dev19 07 Aug 2026 none — — Details →
1.12.0.dev18 06 Aug 2026 none — — Details →
1.12.0.dev17 05 Aug 2026 none — — Details →
1.12.0.dev16 05 Aug 2026 none — — Details →

The newest 120 of 352 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 9

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 9 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for langflow-base

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-105697: Langflow OS Command Injection Vulnerability Leading to Remote Code Execution 9.9 critical 0.10.3 15 Oct 2026
CVE-2025-3248: Langflow Unauthenticated Remote Code Execution Vulnerability 9.3 critical 0.3.0 29 Jun 2026
CVE-2026-21445: Langflow Critical API Endpoints Lacking Authentication 8.8 high 1.5.1 02 Jan 2026
CVE-2025-57760: Langflow Privilege Escalation via CLI Superuser Creation 8.8 high 0.5.1 07 Jul 2026
CVE-2026-21445: Langflow API Authentication Bypass Vulnerability 8.8 high 0.7.1 13 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About langflow-base

Is langflow-base safe to use?

Vulert records 9 vulnerabilities for langflow-base in PyPI: 0 critical, 1 high, 1 medium and 0 low, plus 7 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is langflow-base's Vulert package health score?

Vulert scores langflow-base 71/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of langflow-base affected?

No. 1.14.0.dev3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does langflow-base have?

9 vulnerabilities are recorded for langflow-base in the PyPI ecosystem: 0 critical, 1 high, 1 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new langflow-base vulnerabilities disclosed?

9 vulnerabilities were recorded for langflow-base in the last 12 months, and the oldest entry in this database dates to 02 Jan 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of langflow-base are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor langflow-base for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the langflow-base version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.