CVE-2026-61549

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th 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
9.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.3%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Woodpecker is a CI/CD engine. From 1.0.0 until 3.16.0, pipeline/backend/kubernetes/backend_options.go defines backend_options.kubernetes.serviceAccountName, and the Kubernetes backend in pipeline/backend/kubernetes/pod.go copies that pipeline-step value directly into the pod specification without administrator authorization. Any user with Push permission on a connected repository can therefore run pipeline pods under an arbitrary ServiceAccount in the pipeline namespace and inherit that account's RBAC permissions. When a privileged ServiceAccount is reachable, the attacker can exfiltrate secrets such as database credentials, API keys, and TLS certificates and may take over the cluster. This issue is fixed in version 3.16.0.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation0.3% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.3%
EPSS %ILE
18th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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

July 14, 2026

Last Modified

September 30, 2026

Advisory Details (5)

Auto-updated Sep 15, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

3.16.0

Patch available: woodpecker-ci/woodpecker v3.16.0

https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.16.0
GitHub commit

commit 609ba481b5e9 (woodpecker-ci/woodpecker)

Fix landed in woodpecker-ci/woodpecker commit 609ba481b5e9 — awaiting tagged release

https://github.com/woodpecker-ci/woodpecker/commit/609ba481b5e912f59aaae8ca7bc22b44523c5e37
GitHub commit

commit 5df9d5226062 (woodpecker-ci/woodpecker)

Fix landed in woodpecker-ci/woodpecker commit 5df9d5226062 — awaiting tagged release

https://github.com/woodpecker-ci/woodpecker/commit/5df9d52260626c074c6caafb2dc83d3bc6b53be1
GitHub pull request

Gate Kubernetes serviceAccountName backend step config behind agent config

Fix merged in woodpecker-ci/woodpecker PR #6792 on 2026-06-27 — awaiting tagged release

https://github.com/woodpecker-ci/woodpecker/pull/6792
GitHub advisoryMentions a patch (unverified)

Privilege escalation via unrestricted serviceAccountName in the Kubernetes backend · Advisory · woodpecker-ci/woodpecker · GitHub

https://github.com/woodpecker-ci/woodpecker/security/advisories/GHSA-qf34-295c-26v8

Vendor Advisories for CVE-2026-61549(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 1 ecosystem)
Go(4)
PackageVulnerable rangeFix by version rangeDependents
github.com/woodpecker-ci/woodpecker—
  • 1.0.0 through 1.0.4: no fix on record
  • 1.0.0 on: no fix on record
—
go.woodpecker-ci.org/woodpecker—
  • every version on: no fix on record
—
go.woodpecker-ci.org/woodpecker/v2—
  • every version through 2.8.3: no fix on record
  • every version on: no fix on record
—
go.woodpecker-ci.org/woodpecker/v3—
  • every version up to 3.16.0: fixed in 3.16.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 36× 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-10-14 01:50 UTCEG score recompute
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-10-12 22:05 UTCEG score recompute
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-12 15:50 UTCEG score recompute
  6. 2026-10-11 19:34 UTCEG score recompute
  7. 2026-10-11 16:49 UTCEG score recompute
  8. 2026-10-11 14:11 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-09-30 18:11 UTCEG score recompute
  21. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-09-28 08:51 UTCEG score recompute
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-09-24 08:58 UTCEG score recompute
Show 15 more
  1. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-09-23 03:26 UTCEG score recompute
  3. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-09-18 04:49 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-09-16 04:22 UTCEG score recompute
  8. 2026-09-15 16:35 UTCEG score recompute
  9. 2026-09-15 15:25 UTCEG score recompute
  10. 2026-09-15 14:58 UTCEG score recomputeFirst assessed: 9.0 CRITICAL
  11. 2026-09-15 14:57 UTCMITRE cvelistV5CVSS v3 → 9 · CVSS v4 → 9 · severity → CRITICAL
  12. 2026-08-01 09:51 UTCEG score recompute
  13. 2026-07-26 11:41 UTCEG score recompute
  14. 2026-07-23 03:21 UTCEG score recompute
  15. 2026-07-14 20:56 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

5 shown

Go:go.woodpecker-ci.org/woodpecker/v3 · Go:go.woodpecker-ci.org/woodpecker · Go:github.com/woodpecker-ci/woodpecker

Frequently asked(5)

What is CVE-2026-61549?
CVE-2026-61549 is a critical-severity vulnerability; its CVE record was published on July 14, 2026. Woodpecker is a CI/CD engine. From 1.0.0 until 3.16.0, pipeline/backend/kubernetes/backendoptions.go defines backendoptions.kubernetes.serviceAccountName, and the Kubernetes backend in pipeline/backend/kubernetes/pod.go copies that pipeline-step value directly into the pod specification without…
When was the CVE record for CVE-2026-61549 published?
The CVE record for CVE-2026-61549 was published on July 14, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61549 actively exploited?
CVE-2026-61549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61549?
CVE-2026-61549 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61549?
A fix for CVE-2026-61549 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61549 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61549

Explore →

Is Your Infrastructure Affected by CVE-2026-61549?

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

Book a Demo →Browse All CVEs