CVE-2026-55839: Kestra: Stored XSS via custom Markdown [[link]] attribute injection

Published Aug 18, 2026
·
Updated

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/markdownplugins/link.ts ui/src/utils/markdown.ts ui/src/components/layout/Markdown.vue

The vulnerable code path renders parsed attributes directly into an HTML string:

ts 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:

yaml id: markdownxssflowdesc 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:

text 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:

1. Allowlist only the exact attributes required by the custom router link component. 2. Reject all attributes beginning with on, such as onclick, onmouseover, and onfocus. 3. Reject or sanitize dangerous attributes such as style. 4. HTML-escape all attribute values before rendering. 5. Ensure attributes are joined safely with spaces. 6. Sanitize the final rendered Markdown output before passing it to v-html. 7. Add regression tests for custom [[link]] payloads containing event-handler attributes.

Minimal payload

md [[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.

Other sources

Kestra is an open-source, event-driven orchestration platform. Prior to 1.3.24, Kestra's custom Markdown parser in ui/src/utils/markdownplugins/link.ts allows a user with permission to create or update a Flow description to inject JavaScript event-handler attributes through the custom [[link]] syntax, causing stored cross-site scripting when another user opens the description or information panel in the Flow list. This issue is fixed in version 1.3.24.

MITRE

Affected Software

2 affected componentsFixes available
Kestra Kestra<1.3.24
maven/io.kestra:kestra<1.3.24
1.3.24

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.kestra:kestra to a version that resolves this vulnerability.

    Fixed in 1.3.24
  2. Upgrade

    Upgrade Kestra to a version that resolves this vulnerability.

    Fixed in 1.3.24
  3. Configuration

    Update the custom `[[link ...]]` Markdown attribute handling to reject any attribute names that begin with `on` (e.g., `onclick`, `onmouseover`, `onfocus`) and to reject or sanitize dangerous attributes such as `style` before generating the `<router-md ...>` element.

    Kestra UI custom Markdown link renderer (ui/src/utils/markdown_plugins/link.ts / ui/src/utils/markdown.ts) Allowlist/sanitization of attributes for custom [[link ...]] -> <router-md> = Reject all attributes beginning with `on` and reject/sanitize dangerous attributes such as `style`
  4. Configuration

    Ensure the final rendered Markdown output is sanitized before being passed to `v-html`, and HTML-escape all attribute values when building the generated HTML for the custom `[[link ...]]` syntax.

    Kestra UI Markdown rendering pipeline Sanitize rendered Markdown output before v-html = HTML-escape all attribute values; sanitize final rendered Markdown output
  5. Configuration

    Modify the custom link renderer so attribute tokens are joined safely with spaces (rather than unsafe concatenation), ensuring attacker-controlled attributes cannot break out of the intended element attribute context.

    Kestra custom [[link]] attribute construction Attribute joining / string building = Join attributes safely with spaces
  6. Operational

    Add regression tests for custom `[[link ...]]` payloads containing event-handler attributes, and verify that the renderer rejects `on*` attributes and does not allow dangerous attributes (e.g., `style`).

Event History

Aug 18, 2026
CVE Published
via MITRE·03:27 PM
Data Sourced
via MITRE·03:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·04:31 PM
Data Sourced
via GitHub·04:31 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue, and who is exposed to the stored payload?

Users who can create or update Flow descriptions can introduce the malicious content. The payload executes when another user opens the affected Flow description or its information panel in the Flow list.

2

What access and interaction are required for exploitation?

Exploitation requires low-level privileges to create or modify a Flow description and user interaction from a victim who opens the description or information panel. The vulnerable input is the custom [[link]] Markdown syntax, which can be used to inject JavaScript event-handler attributes.

3

What version contains the fix?

Upgrade Kestra to version 1.3.24, which fixes the issue.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203