CVE-2026-58370

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-30. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.1Exploit: NoneExposed: 0

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

Woodpecker before 3.15.0 matches the ApprovalAllowedUsers bypass list against pipeline.Author. For the GitLab forge driver, pipeline.Author is populated from the git commit author name (commit.author.name) carried in the webhook payload, which is attacker-controlled and not verified by GitLab. A user who can open a merge request from a fork can set the commit author name to match an entry in ApprovalAllowedUsers, causing needsApproval to return false so the pipeline runs without the required approval. This defeats the fork-approval security boundary and allows execution of attacker-controlled pipeline steps on a Woodpecker agent and exfiltration of CI secrets exposed to the run. Other built-in forge drivers (Gitea, Forgejo, GitHub, Bitbucket) derive pipeline.Author from the forge-validated sender/actor identity and are not affected.

CVSS v3
8.1
EG Score
8.1(high)
EPSS
41.8%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 2, 2026

Advisory Details (4)

Auto-updated Jun 30, 2026
Patch available. Sources: github_commit, github_pr, github_release.
generic

Woodpecker < 3.15.0 - GitLab Approval Gate Bypass via Spoofable Commit Author Name | Advisories | VulnCheck

https://www.vulncheck.com/advisories/woodpecker-gitlab-approval-gate-bypass-via-spoofable-commit-author-name
github_release Patch Available

3.15.0

Patch available: woodpecker-ci/woodpecker v3.15.0

https://github.com/woodpecker-ci/woodpecker/releases/tag/v3.15.0
github_pr

Use Gitlab username

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

https://github.com/woodpecker-ci/woodpecker/pull/6653
github_commit

commit 98faae778c95 (woodpecker-ci/woodpecker)

Fix landed in woodpecker-ci/woodpecker commit 98faae778c95 — awaiting tagged release

https://github.com/woodpecker-ci/woodpecker/commit/98faae778c953678944996c89ed99307d2f16a3d

Vendor Advisories for CVE-2026-58370(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 38× in last 7d / 38× 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-07-06 20:13 UTCEG score recompute
  2. 2026-07-06 20:13 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 09:00 UTCEG score recompute
  6. 2026-07-06 09:00 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 21:48 UTCEG score recompute
  10. 2026-07-05 21:48 UTCGHSA enrichment
  11. 2026-07-05 10:36 UTCEG score recompute
  12. 2026-07-05 10:36 UTCGHSA enrichment
  13. 2026-07-05 02:31 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 23:22 UTCEG score recompute
  16. 2026-07-04 23:22 UTCGHSA enrichment
  17. 2026-07-04 12:08 UTCEG score recompute
  18. 2026-07-04 12:08 UTCGHSA enrichment
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 00:54 UTCEG score recompute
  22. 2026-07-04 00:54 UTCGHSA enrichment
  23. 2026-07-03 13:43 UTCEG score recompute
  24. 2026-07-03 13:43 UTCGHSA enrichment
  25. 2026-07-03 02:32 UTCEG score recompute
Show 13 more
  1. 2026-07-03 02:32 UTCGHSA enrichment
  2. 2026-07-02 15:21 UTCEG score recompute
  3. 2026-07-02 15:20 UTCGHSA enrichment
  4. 2026-07-02 04:09 UTCEG score recompute
  5. 2026-07-02 04:08 UTCGHSA enrichment
  6. 2026-07-01 16:57 UTCEG score recompute
  7. 2026-07-01 16:57 UTCGHSA enrichment
  8. 2026-07-01 15:07 UTCEPSS rescore
  9. 2026-07-01 05:46 UTCEG score recompute
  10. 2026-07-01 05:46 UTCGHSA enrichment
  11. 2026-06-30 18:33 UTCEG score recompute
  12. 2026-06-30 18:33 UTCGHSA enrichment
  13. 2026-06-30 18:32 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58370?
CVE-2026-58370 is a high vulnerability published on June 30, 2026. Woodpecker before 3.15.0 matches the ApprovalAllowedUsers bypass list against pipeline.Author. For the GitLab forge driver, pipeline.Author is populated from the git commit author name (commit.author.name) carried in the webhook payload, which is attacker-controlled and not verified by GitLab. A…
When was CVE-2026-58370 disclosed?
CVE-2026-58370 was first published in the National Vulnerability Database on June 30, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58370 actively exploited?
CVE-2026-58370 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58370?
CVE-2026-58370 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-58370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58370, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-58370?

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

Start Free Scan →Browse All CVEs