How severe is GHSA-rvqx-wpfh-mfx7?

No CVSS score has been assigned to GHSA-rvqx-wpfh-mfx7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rvqx-wpfh-mfx7?

GHSA-rvqx-wpfh-mfx7 affects the following packages: langflow (PyPI), langflow-base (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-rvqx-wpfh-mfx7?

Update langflow to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvqx-wpfh-mfx7 is resolved across your whole dependency graph.

How do I detect GHSA-rvqx-wpfh-mfx7 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rvqx-wpfh-mfx7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rvqx-wpfh-mfx7?

O3 pinpoints whether GHSA-rvqx-wpfh-mfx7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rvqx-wpfh-mfx7 actively exploited in the wild?

Yes. There are 8 known exploit references for GHSA-rvqx-wpfh-mfx7, including 2 documented proof-of-concept exploits on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-rvqx-wpfh-mfx7?

GHSA-rvqx-wpfh-mfx7 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-rvqx-wpfh-mfx7 in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-rvqx-wpfh-mfx7 (Langflow Missing Authentication Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-05-05. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-05-26. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-rvqx-wpfh-mfx7?

GHSA-rvqx-wpfh-mfx7 is classified as Missing Authentication (CWE-306), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-rvqx-wpfh-mfx7?

A Nuclei detection template exists for GHSA-rvqx-wpfh-mfx7, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-rvqx-wpfh-mfx7 published, and has it been updated?

GHSA-rvqx-wpfh-mfx7 was published on June 17, 2025 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-05-05 — agencies required to remediate by 2025-05-26 · Ransomware

🐍 PyPI

GHSA-rvqx-wpfh-mfx7

GHSA-rvqx-wpfh-mfx7 is a Missing Authentication vulnerability in langflow. It is in CISA's Known Exploited Vulnerabilities catalog (added 2025-05-05) and has been used in ransomware campaigns — treat it as actively exploited and patch now. O3 Security confirms whether GHSA-rvqx-wpfh-mfx7 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Langflow Unauth RCE

Also known asCVE-2025-3248PYSEC-2025-36PYSEC-2026-380

Published

Jun 17, 2025

Updated

Jun 29, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

8 known

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐍langflow🐍langflow-base

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Langflow versions prior to 1.3.0 are susceptible to code injection in the /api/v1/validate/code endpoint. A remote and unauthenticated attacker can send crafted HTTP requests to execute arbitrary code.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`langflow`	all versions	1.3.0
🐍PyPI	`langflow-base`	all versions	0.3.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52364webappsmultiple

Langflow 1.2.x - Remote Code Execution (RCE)

by Raghad Abdallah Al-syouf · Jul 16, 2025

Exploit-DB Source

EDB-52262remotemultiple

Langflow 1.3.0 - Remote Code Execution (RCE)

by VeryLazyTech · Apr 18, 2025

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update langflow to 1.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvqx-wpfh-mfx7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rvqx-wpfh-mfx7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rvqx-wpfh-mfx7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-rvqx-wpfh-mfx7 in your dependencies?

O3 detects GHSA-rvqx-wpfh-mfx7 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works