Quick answers
- Is CVE-2026-68919 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-68919 being exploited in the wild.
- How severe is CVE-2026-68919?
- Informational severity, published 21 September 2026.
- Which products and versions are affected?
- GoCD 13.3.0 to 26.0.x.
- Is there a fix for CVE-2026-68919?
- A patch was published on 2026-07-05: Fix merged and released in version 26.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-68919 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-68919?
- Check whether you run GoCD at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stored XSS flaw in how GoCD renders package material modification comments across multiple UI views (Stage Detail, Job/Build Detail, Value Stream Map, Pipeline History). Attackers with write access to materials tracked by GoCD can craft forged package material comments that mimic the trackback format and bypass encoding/escaping mechanisms. Exploitation requires a victim to view a page that renders the malicious comment, and the attack vector is network-based through a user's authenticated session.
Affected products
- GoCD GoCD 13.3.0 to 26.0.x
Timeline
- 2026-09-21: disclosed
- 2026-07-05: patched: Fix merged and released in version 26.1.0