# CVE-2026-7687: langflow-ai langflow Full Builtins code_parser.py CodeParser.parse_callable_details command injection

> Remote attackers can execute arbitrary commands via the Full Builtins Module Handler in Langflow, requiring immediate mitigation due to public exploit availability.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2026
- **Updated:** 5 May 2026
- **Also known as:** GHSA-pprg-5xr3-4qr4

## What is CVE-2026-7687?

CVE-2026-7687 is a medium-severity command injection vulnerability in langflow-ai langflow, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was determined in langflow-ai langflow up to 1.8.4. Affected by this issue is the function CodeParser.parse_callable_details of the file src/lfx/src/lfx/custom/code_parser/code_parser.py of the component Full Builtins Module Handler. Executing a manipulation can lead to command injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-7687?


## How do I fix CVE-2026-7687?

No fix has been published for CVE-2026-7687 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-7687 being exploited?

There is no known exploitation of CVE-2026-7687 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7687 and fix it if it is affected.

What it is: CVE-2026-7687 is a medium-severity command injection vulnerability in langflow-ai langflow, published on 3 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7687 in the wild and no public exploit code.

Affected product: langflow-ai langflow. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7687/ (Markdown: https://insights.sbomify.com/CVE-2026-7687/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7687
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7687
- OSV: https://osv.dev/vulnerability/CVE-2026-7687

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7687/
Summaries are generated and may contain mistakes; the official description above is the record.