CVE-2026-58370

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM 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 — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 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(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

June 30, 2026

Last Modified

July 14, 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 11× in last 7d / 48× 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.

Showing the most recent 100 of 231 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:49 UTCEG score recompute
  3. 2026-09-18 06:49 UTCGHSA enrichment
  4. 2026-09-17 19:31 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 03:11 UTCEPSS rescore
  8. 2026-09-14 00:47 UTCEG score recompute
  9. 2026-09-14 00:47 UTCGHSA enrichment
  10. 2026-09-13 16:47 UTCEPSS rescore
  11. 2026-09-13 09:16 UTCGHSA enrichment
  12. 2026-09-12 15:09 UTCEG score recompute
  13. 2026-09-12 15:09 UTCGHSA enrichment
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-08 22:01 UTCEPSS rescore
  17. 2026-09-07 16:01 UTCEPSS rescore
  18. 2026-09-06 14:35 UTCEG score recompute
  19. 2026-09-06 14:35 UTCGHSA enrichment
  20. 2026-09-06 13:47 UTCEPSS rescore
  21. 2026-09-04 05:07 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 18:03 UTCEG score recompute
  2. 2026-08-30 18:03 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 22:41 UTCEG score recompute
  6. 2026-08-27 22:41 UTCGHSA enrichment
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 21:44 UTCEG score recompute
  11. 2026-08-24 21:44 UTCGHSA enrichment
  12. 2026-08-24 06:42 UTCGHSA enrichment
  13. 2026-08-23 18:56 UTCGHSA enrichment
  14. 2026-08-23 07:44 UTCEG score recompute
  15. 2026-08-23 07:44 UTCGHSA enrichment
  16. 2026-08-23 00:19 UTCEPSS rescore
  17. 2026-08-22 20:33 UTCGHSA enrichment
  18. 2026-08-22 08:21 UTCEG score recompute
  19. 2026-08-22 08:21 UTCGHSA enrichment
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-21 17:20 UTCGHSA enrichment
  22. 2026-08-21 04:49 UTCEG score recompute
  23. 2026-08-21 04:49 UTCGHSA enrichment
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 16:55 UTCGHSA enrichment
  26. 2026-08-20 05:31 UTCEG score recompute
  27. 2026-08-20 05:31 UTCGHSA enrichment
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 10:27 UTCGHSA enrichment
  30. 2026-08-18 23:01 UTCEG score recompute
  31. 2026-08-18 23:00 UTCGHSA enrichment
  32. 2026-08-18 13:48 UTCEPSS rescore
  33. 2026-08-18 00:03 UTCEG score recompute
  34. 2026-08-18 00:03 UTCGHSA enrichment
  35. 2026-08-17 13:47 UTCEPSS rescore
  36. 2026-08-17 09:20 UTCGHSA enrichment
  37. 2026-08-16 22:09 UTCEG score recompute
  38. 2026-08-16 22:09 UTCGHSA enrichment
  39. 2026-08-16 14:56 UTCEPSS rescore
  40. 2026-08-16 10:58 UTCEG score recompute
  41. 2026-08-16 10:58 UTCGHSA enrichment
  42. 2026-08-16 02:14 UTCEPSS rescore
  43. 2026-08-15 23:47 UTCGHSA enrichment
  44. 2026-08-15 12:36 UTCEG score recompute
  45. 2026-08-15 12:36 UTCGHSA enrichment
  46. 2026-08-15 01:30 UTCEPSS rescore
  47. 2026-08-15 01:24 UTCGHSA enrichment
  48. 2026-08-14 14:13 UTCGHSA enrichment
  49. 2026-08-14 03:01 UTCEG score recompute
  50. 2026-08-14 03:01 UTCGHSA enrichment
  51. 2026-08-13 22:00 UTCEPSS rescore
  52. 2026-08-13 15:50 UTCGHSA enrichment
  53. 2026-08-13 04:17 UTCGHSA enrichment
  54. 2026-08-12 17:06 UTCEG score recompute
  55. 2026-08-12 17:06 UTCGHSA enrichment
  56. 2026-08-12 13:51 UTCEPSS rescore
  57. 2026-08-12 05:54 UTCGHSA enrichment
  58. 2026-08-11 18:25 UTCEG score recompute
  59. 2026-08-11 18:25 UTCGHSA enrichment
  60. 2026-08-11 06:59 UTCEG score recompute
  61. 2026-08-11 06:59 UTCGHSA enrichment
  62. 2026-08-11 00:00 UTCEPSS rescore
  63. 2026-08-10 19:48 UTCGHSA enrichment
  64. 2026-08-10 08:36 UTCGHSA enrichment
  65. 2026-08-09 21:25 UTCEG score recompute
  66. 2026-08-09 21:25 UTCGHSA enrichment
  67. 2026-08-09 13:46 UTCEPSS rescore
  68. 2026-08-09 10:14 UTCGHSA enrichment
  69. 2026-08-08 23:03 UTCEG score recompute
  70. 2026-08-08 23:03 UTCGHSA enrichment
  71. 2026-08-08 16:37 UTCEPSS rescore
  72. 2026-08-08 11:51 UTCGHSA enrichment
  73. 2026-08-08 00:40 UTCEG score recompute
  74. 2026-08-08 00:40 UTCGHSA enrichment
  75. 2026-08-07 13:29 UTCGHSA enrichment

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 14, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 47.6% of all scored CVEs.
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.