GHSA-34pm-923j-7wf8 is a high-severity (CVSS 8.7) Cross-site Scripting (XSS) vulnerability in io.kestra:kestra. A fix is available for io.kestra:kestra — see the affected versions and patch details below.
Kestra vulnerable to stored XSS via custom Markdown [[link]] attribute injection
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-34pm-923j-7wf8.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-34pm-923j-7wf8 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 382,205 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
io.kestra:kestraReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Kestra’s Markdown renderer supports a custom [[link ...]] syntax that is converted into a custom HTML element. The custom Markdown parser allows attacker-controlled attributes to be rendered into the generated element without proper allowlisting or sanitization.
As a result, a user who can create or edit Markdown-rendered content, such as a Flow description, can inject JavaScript event-handler attributes. When another user views or interacts with the affected Markdown-rendered UI element, the JavaScript executes in that user’s browser.
This is not a normal raw-HTML Markdown payload such as <img onerror=...>. The payload uses Kestra’s custom [[link]] Markdown syntax, and the dangerous HTML attributes are introduced by Kestra’s own Markdown plugin.
Affected version
Tested on Kestra 1.3.22.
Affected components
Source review identified the issue in the custom Markdown link renderer:
ui/src/utils/markdown_plugins/link.tsui/src/utils/markdown.tsui/src/components/layout/Markdown.vue
The vulnerable code path renders parsed attributes directly into an HTML string:
const attrs = token.attrs
? token.attrs.map(([name, value]) => `${name}="${value}"`).join("")
: "";
return `<router-md ${attrs}>`;
The implementation does not safely restrict attribute names or values before inserting the generated HTML into the DOM.
Proof of concept
Create or edit a Flow with the following YAML:
id: markdown_xss_flow_desc
namespace: company.team
description: |
[[link x="y" style="position:fixed;inset:0;z-index:9999;background:rgba(255,0,0,0.05)" onmouseover="alert(document.domain)"]]
tasks:
- id: hello
type: io.kestra.plugin.core.log.Log
message: hello
Save the Flow.
Then navigate to the Flow list:
http://localhost:8080/ui/main/flows
Click the description/info icon next to the malicious Flow.
Actual result
The browser executes JavaScript from the Flow description. In the PoC, an alert is triggered showing the current domain.
Expected result
Markdown-rendered Flow descriptions should not be able to inject arbitrary JavaScript event handlers or attacker-controlled HTML attributes into the page.
The custom [[link]] syntax should only generate safe attributes required for the intended router-link behavior.
Security impact
An attacker with permission to create or update a Flow in a namespace can store a malicious Markdown payload in the Flow description. When another Kestra user views the Flow list and opens the Flow description/info panel, attacker-controlled JavaScript executes in the victim’s browser.
Depending on the victim’s privileges, this may allow the attacker to perform actions as the victim within the Kestra UI, access data visible to the victim, or pivot into more privileged namespace or administrative functionality.
This crosses a security boundary in multi-user Kestra deployments where Flow authors are less privileged than administrators or other operators who review workflows.
Suggested remediation
The custom Markdown link plugin should not render arbitrary attributes into raw HTML.
Recommended fixes:
- Allowlist only the exact attributes required by the custom router link component.
- Reject all attributes beginning with
on, such asonclick,onmouseover, andonfocus. - Reject or sanitize dangerous attributes such as
style. - HTML-escape all attribute values before rendering.
- Ensure attributes are joined safely with spaces.
- Sanitize the final rendered Markdown output before passing it to
v-html. - Add regression tests for custom
[[link]]payloads containing event-handler attributes.
Minimal payload
[[link x="y" style="position:fixed;inset:0;z-index:9999;background:rgba(255,0,0,0.05)" onmouseover="alert(document.domain)"]]
Evidence collected
- The payload was stored in a Flow description.
- The Flow list displayed the malicious Flow.
- Opening the Flow description/info panel triggered JavaScript execution in the browser.
- The payload did not require execution of the Flow.
- The payload used Kestra’s custom
[[link]]syntax rather than raw HTML.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.kestra:kestra | all versions | 1.3.24io.kestra:kestra:1.3.24 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.kestra:kestra, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.kestra:kestra to 1.3.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-34pm-923j-7wf8 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-34pm-923j-7wf8 in your dependencies?
Find it across Maven, including transitive dependencies.