{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-52741 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-52741 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-52741 is a high-severity cross-site scripting vulnerability in gocd, published on 21 Sep 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-52741 and fix it if it is affected.\n\nWhat it is: CVE-2026-52741 is a high-severity cross-site scripting vulnerability in gocd, published on 21 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-52741 in the wild and no public exploit code.\n\nAffected product: gocd. 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-52741/ (Markdown: https://insights.sbomify.com/CVE-2026-52741/index.md)","id":"CVE-2026-52741","markdown":"https://insights.sbomify.com/CVE-2026-52741/index.md","name":"CVE-2026-52741","record":{"aliases":["GHSA-hj3c-q23m-fxcg"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"GoCD continuous delivery server","requires_auth":"low_privilege","summary":"An attacker with commit access can inject malicious scripts via commit comments, leading to stored XSS and potential session hijacking or unauthorized actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"description":"GoCD is a continuous deliver server. From 18.3.0 until 26.1.0, GoCD can generate unescaped tracking-tool links from commit comments when a project uses a lenient Tracking Tool regular expression with an ID capturing group, such as JIRA-(.+). An attacker with commit access to a tracked material can place URI or HTML special characters in a matching commit comment, causing stored cross-site scripting when a victim views an affected Compare Pipeline page. Deployments without Tracking Tool integration, without an ID capturing group, or with conservative matchers that cannot match special characters are not affected. Successful exploitation can expose a privileged user session or allow changes using the victim's credentials and privileges. This issue is fixed in version 26.1.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"GoCD has stored XSS possible via tracking tool link highlighting on Compare Pipeline pages","id":"CVE-2026-52741","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"GoCD is vulnerable to historical server configuration API authorization bypass","id":"CVE-2026-52742"},"packages":[],"prev":{"headline":"GoCD is vulnerable to pipeline template view API authorization bypass","id":"CVE-2026-52740"},"products":["gocd"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["gocd"]},"summary":"An attacker with commit access can inject malicious scripts via commit comments, leading to stored XSS and potential session hijacking or unauthorized actions.","url":"https://insights.sbomify.com/CVE-2026-52741/"}