Stored XSS via link attribute injection
Published Aug 18, 2026 · Updated Aug 18, 2026
Stored XSS in Flow descriptions in Kestra before 1.3.24 allows remote authenticated users to execute script in another user's browser. Kestra's custom Markdown link renderer in ui/src/utils/markdown_plugins/link.ts copied parsed [[link]] attributes into generated HTML and, before the fix, did not restrict attribute names beyond basic parsing, allowing event-handler attributes such as onmouseover to reach the rendered router-md element. Exploitation requires permission to create or update a Flow description and a second user to open the description or information panel; the injected script then runs with the viewer's Kestra UI access and can read visible data or perform actions as that user.
Summary
What happened
Stored XSS in Flow descriptions in Kestra before 1.3.24 allows remote authenticated users to execute script in another user's browser. Kestra's custom Markdown link renderer in ui/src/utils/markdown_plugins/link.ts copied parsed [[link]] attributes into generated HTML and, before the fix, did not restrict attribute names beyond basic parsing, allowing event-handler attributes such as onmouseover to reach the rendered router-md element. Exploitation requires permission to create or update a Flow description and a second user to open the description or information panel; the injected script then runs with the viewer's Kestra UI access and can read visible data or perform actions as that user.
The record
- CVE
- CVE-2026-55839
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Kestra
- Product
- Kestra
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.24
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA proof of concept for Flow-description stored XSSproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo