CVE-2026-68919

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-83948 (ENISA EUVD)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 21, 2026

Last Modified

September 25, 2026

Advisory Details (4)

Auto-updated Sep 21, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

Releases - Version notes | GoCD

https://www.gocd.org/releases/#26-1-0
GitHub release Patch Available

GoCD 26.1.0

Patch available: gocd/gocd 26.1.0

https://github.com/gocd/gocd/releases/tag/26.1.0
GitHub commit Patch Available

commit a03eeeaa4a85 (gocd/gocd)

Patch available: gocd/gocd 26.1.0 (contains commit a03eeeaa4a85)

https://github.com/gocd/gocd/commit/a03eeeaa4a85edfc9053e743610547d4fcf7aea6
GitHub advisoryMentions a patch (unverified)

GoCD before 26.1.0 has stored XSS possible via forged package material comments on Stage/Job/VSM pages · Advisory · gocd/gocd · GitHub

https://github.com/gocd/gocd/security/advisories/GHSA-pp5x-wgv2-g37p

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-27 20:11 UTCEG score recompute
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-25 14:09 UTCEG score recompute
  12. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-20 09:45 UTCEG score recompute
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-18 03:19 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  22. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
Show 48 more
  1. 2026-10-13 09:59 UTCEG score recompute
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-12 15:44 UTCEG score recompute
  4. 2026-10-11 19:29 UTCEG score recompute
  5. 2026-10-11 16:45 UTCEG score recompute
  6. 2026-10-11 14:06 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-11 11:23 UTCEG score recompute
  9. 2026-10-11 00:21 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-10 02:17 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-08 17:19 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-08 05:55 UTCEG score recompute
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-06 21:05 UTCEG score recompute
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  19. 2026-10-05 22:57 UTCEG score recompute
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-05 01:04 UTCEG score recompute
  22. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-03 15:56 UTCEG score recompute
  24. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  25. 2026-10-02 18:02 UTCEG score recompute
  26. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  27. 2026-10-01 20:09 UTCEG score recompute
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-09-30 22:14 UTCEG score recompute
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  31. 2026-09-30 00:21 UTCEG score recompute
  32. 2026-09-29 01:25 UTCEG score recompute
  33. 2026-09-28 14:29 UTCEG score recompute
  34. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-09-27 16:30 UTCEG score recompute
  36. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  37. 2026-09-26 18:36 UTCEG score recompute
  38. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  39. 2026-09-26 07:37 UTCEG score recompute
  40. 2026-09-25 20:39 UTCEG score recompute
  41. 2026-09-25 19:29 UTCEG score recompute
  42. 2026-09-24 20:00 UTCEG score recompute
  43. 2026-09-23 22:06 UTCEG score recompute
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-09-23 00:13 UTCEG score recompute
  46. 2026-09-21 15:22 UTCEG score recompute
  47. 2026-09-21 15:00 UTCEG score recomputeFirst assessed: 7.0 HIGH
  48. 2026-09-21 15:00 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68919?
CVE-2026-68919 is a high-severity vulnerability; its CVE record was published on September 21, 2026. 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…
When was the CVE record for CVE-2026-68919 published?
The CVE record for CVE-2026-68919 was published on September 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 25, 2026; the record at its source may have been updated since.
Is CVE-2026-68919 actively exploited?
CVE-2026-68919 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68919?
CVE-2026-68919 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68919?
A fix for CVE-2026-68919 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68919

Explore →

Is Your Infrastructure Affected by CVE-2026-68919?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs