How severe is GHSA-g22f-v6f7-2hrh?

No CVSS score has been assigned to GHSA-g22f-v6f7-2hrh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g22f-v6f7-2hrh?

GHSA-g22f-v6f7-2hrh affects the following packages: langflow (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-g22f-v6f7-2hrh?

No patched version of langflow has shipped for GHSA-g22f-v6f7-2hrh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-g22f-v6f7-2hrh in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g22f-v6f7-2hrh 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.

Is GHSA-g22f-v6f7-2hrh actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-g22f-v6f7-2hrh, including 1 documented proof-of-concept exploit 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-g22f-v6f7-2hrh?

GHSA-g22f-v6f7-2hrh has an EPSS (Exploit Prediction Scoring System) score of 63.8%, placing it in the 99th 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-g22f-v6f7-2hrh in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-g22f-v6f7-2hrh (Langflow Inclusion of Functionality from Untrusted Control Sphere Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-07-21. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-07-24. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. 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-g22f-v6f7-2hrh?

GHSA-g22f-v6f7-2hrh is classified as CWE-829 (CWE-829). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-g22f-v6f7-2hrh?

A Nuclei detection template exists for GHSA-g22f-v6f7-2hrh, 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-g22f-v6f7-2hrh published, and has it been updated?

GHSA-g22f-v6f7-2hrh was published on January 23, 2026 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

CISA KEV · ACTIVELY EXPLOITED

GHSA-g22f-v6f7-2hrh — langflow

GHSA-g22f-v6f7-2hrh is a CWE-829 vulnerability in langflow. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-07-21) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Langflow affected by Remote Code Execution via validate_code() exec()

Also known asCVE-2026-0770PYSEC-2026-1525

Published

Jan 23, 2026

Updated

Jul 7, 2026

Affected

1 pkg

Patched

See advisory

Exploits

2 known

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-07-21. Federal agencies were required to remediate by 2026-07-24.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for GHSA-g22f-v6f7-2hrh.

EPSS Exploitation Probability

via FIRST.org ↗

63.8%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍langflow

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

The specific flaw exists within the handling of the exec_globals parameter provided to the validate endpoint. The issue results from the inclusion of a resource from an untrusted control sphere. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-27325.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`langflow`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

langflowlangflow

≤ 1.7.3

range

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-52597webappsmultiple

Langflow 1.3.0 - Remote Code Execution

by Diamorphine · May 29, 2026

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of langflow has shipped for GHSA-g22f-v6f7-2hrh yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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 to detect GHSA-g22f-v6f7-2hrh

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-g22f-v6f7-2hrh -u https://target

Template: Langflow < 1.3.0 - Remote Code Execution via validate_code() exec()
Severity: critical
Impact: Remote attackers can execute arbitrary code as root, leading to full system compromise.
Remediation: Update to the latest version of Langflow.

Template by ProjectDiscovery nuclei-templates (affix), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Langflow. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of the exec_globals parameter provided to the validate endpoint. The issue results from the inclusion of a resource from an untrusted control sphere. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-27325.

O3 Security · Impact-Aware SCA

Is GHSA-g22f-v6f7-2hrh in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works