CVE-2026-61549

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.0(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

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
Severity90% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 14, 2026

Last Modified

September 16, 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_pr

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 Patch Available

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 rangeFixed inDependents
github.com/woodpecker-ci/woodpecker———
go.woodpecker-ci.org/woodpecker———
go.woodpecker-ci.org/woodpecker/v2———
go.woodpecker-ci.org/woodpecker/v3—3.16.0—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 04:49 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 04:22 UTCEG score recompute
  5. 2026-09-15 16:35 UTCEG score recompute
  6. 2026-09-15 15:25 UTCEG score recompute
  7. 2026-09-15 14:58 UTCEG score recompute▲ 9.00
  8. 2026-09-15 14:57 UTCMITRE cvelistV5CVSS v3 → 9 · CVSS v4 → 9 · severity → CRITICAL
  9. 2026-08-01 09:51 UTCEG score recompute
  10. 2026-07-26 11:41 UTCEG score recompute
  11. 2026-07-23 03:21 UTCEG score recompute
  12. 2026-07-14 20:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61549?
CVE-2026-61549 is a critical vulnerability 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 CVE-2026-61549 disclosed?
CVE-2026-61549 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61549 actively exploited?
CVE-2026-61549 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.7% of all scored CVEs.
What is the CVSS score of CVE-2026-61549?
CVE-2026-61549 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-61549?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61549, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs