{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33664 exists.","fix":"No fix has been published for CVE-2026-33664 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-33664 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33664 exists.\n\nAffected product: kestra-io kestra. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33664/ (Markdown: https://insights.sbomify.com/CVE-2026-33664/index.md)","id":"CVE-2026-33664","markdown":"https://insights.sbomify.com/CVE-2026-33664/index.md","name":"CVE-2026-33664","record":{"aliases":["GHSA-v2mc-8q95-g7hp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Kestra orchestration platform","requires_auth":"low_privilege","summary":"Attackers can inject malicious JavaScript via flow YAML fields, executing code in victims' browsers to potentially hijack accounts.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kestra","vendor":"kestra"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Kestra Vulnerable to Stored Cross-Site Scripting via Flow YAML Fields","id":"CVE-2026-33664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"n8n: LDAP Email-Based Account Linking Allows Privilege Escalation and Account Takeover","id":"CVE-2026-33665"},"packages":[],"prev":{"headline":"n8n Vulnerable to Credential Theft via Name-Based Resolution and Permission Checker Bypass in Community Edition","id":"CVE-2026-33663"},"products":["kestra"],"published":"2026-03-26","related":[{"cvss_score":10,"headline":"Kestra OSS OS Command Injection","id":"CVE-2026-49869","kev_date_added":"2026-09-02","published":"2026-06-26"},{"cvss_score":10,"headline":"Kestra: Unauthenticated RCE via /configs path-suffix auth-filter bypass","id":"CVE-2026-53576","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":10,"headline":"Kestra: Remote Code Execution via SQL Injection","id":"CVE-2026-34612","kev_date_added":null,"published":"2026-04-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2026-38428","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"Kestra BasicAuth Password Stored as SHA-512 Enables Offline Brute-Force Attack","id":"CVE-2026-55069","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":7.7,"headline":"Kestra: Path traversal via URL-encoded \"%2E%2E\" in execution and namespace file endpoints allows arbitrary file read","id":"CVE-2026-45807","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":7.7,"headline":"Path traversal in kestra","id":"CVE-2026-49984","kev_date_added":null,"published":"2026-06-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-27","vendors":["kestra-io"]},"summary":"Attackers can inject malicious JavaScript via flow YAML fields, executing code in victims' browsers to potentially hijack accounts.","url":"https://insights.sbomify.com/CVE-2026-33664/"}