# CVE-2026-33664: Kestra Vulnerable to Stored Cross-Site Scripting via Flow YAML Fields

> Attackers can inject malicious JavaScript via flow YAML fields, executing code in victims' browsers to potentially hijack accounts.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-v2mc-8q95-g7hp

## What is CVE-2026-33664?

CVE-2026-33664 is a high-severity cross-site scripting vulnerability in kestra-io kestra, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Kestra is an open-source, event-driven orchestration platform Versions up to and including 1.3.3 render user-supplied flow YAML metadata fields — description, inputs[].displayName, inputs[].description — through the Markdown.vue component instantiated with html: true. The resulting HTML is injected into the DOM via Vue's v-html without any sanitization. This allows a flow author to embed arbitrary JavaScript that executes in the browser of any user who views or interacts with the flow. This is distinct from GHSA-r36c-83hm-pc8j / CVE-2026-29082, which covers only FilePreview.vue rendering .md files from execution outputs. The present finding affects different components, different data sources, and requires significantly less user interaction (zero-click for input.displayName). As of time of publication, it is unclear if a patch is available.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Kestra Kestra.

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

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

## Is CVE-2026-33664 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33664 exists.

## Other vulnerabilities in kestra-io kestra

- [CVE-2026-49869](https://insights.sbomify.com/CVE-2026-49869/): Kestra OSS OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2026-53576](https://insights.sbomify.com/CVE-2026-53576/): Kestra: Unauthenticated RCE via /configs path-suffix auth-filter bypass (critical 10.0)
- [CVE-2026-34612](https://insights.sbomify.com/CVE-2026-34612/): Kestra: Remote Code Execution via SQL Injection (critical 10.0)
- [CVE-2026-38428](https://insights.sbomify.com/CVE-2026-38428/): SQL injection in n/a (critical 9.8)
- [CVE-2026-55069](https://insights.sbomify.com/CVE-2026-55069/): Kestra BasicAuth Password Stored as SHA-512 Enables Offline Brute-Force Attack (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33664 is a high-severity cross-site scripting vulnerability in kestra-io kestra, published on 26 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33664 exists.

Affected product: kestra-io kestra. 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-33664/ (Markdown: https://insights.sbomify.com/CVE-2026-33664/index.md)
```

## Sources

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

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