{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68919 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-68919 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-68919 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-68919 and fix it if it is affected.\n\nWhat it is: CVE-2026-68919 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-68919 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-68919/ (Markdown: https://insights.sbomify.com/CVE-2026-68919/index.md)","id":"CVE-2026-68919","markdown":"https://insights.sbomify.com/CVE-2026-68919/index.md","name":"CVE-2026-68919","record":{"aliases":["GHSA-pp5x-wgv2-g37p"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"GoCD continuous delivery server","requires_auth":"low_privilege","summary":"An attacker with material write access can inject malicious scripts into GoCD comments, leading to session hijacking or unauthorized actions when viewed by other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/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 13.3.0 until 26.1.0, GoCD does not correctly encode and escape malicious material modification comments that mimic the special trackback format used by package materials when rendering the Stage Detail, Job/Build Detail, Value Stream Map, and Pipeline History views. A user with write access to a material tracked by GoCD can store arbitrary HTML or JavaScript in a forged package material comment, which executes in the browser session of a user who later views an affected page. Exploitation requires a victim to view a page that renders the malicious modification, and GoCD does not render every material comment in every view. 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 forged package material comments on Stage/Job/VSM pages","id":"CVE-2026-68919","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"DiceBear: SVG injection via the unescaped rotate option in @dicebear/core (and fontSize/fontWeight in @dicebear/initials)","id":"CVE-2026-68921"},"packages":[],"prev":{"headline":"Nicotine+: Decompression of peer messages can exhaust available memory","id":"CVE-2026-68911"},"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-25","vendors":["gocd"]},"summary":"An attacker with material write access can inject malicious scripts into GoCD comments, leading to session hijacking or unauthorized actions when viewed by other users.","url":"https://insights.sbomify.com/CVE-2026-68919/"}