Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 30 Jun 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 30 Jun 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Woodpecker < 3.15.0 - GitLab Approval Gate Bypass via Spoofable Commit Author Name | |
| First Time appeared |
Woodpecker-ci
Woodpecker-ci woodpecker |
|
| Weaknesses | CWE-290 | |
| CPEs | cpe:2.3:a:woodpecker-ci:woodpecker:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Woodpecker-ci
Woodpecker-ci woodpecker |
|
| References |
|
|
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-06-30T17:13:07.424Z
Reserved: 2026-06-30T12:15:07.392Z
Link: CVE-2026-58370
Updated: 2026-06-30T17:06:57.043Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-30T17:30:15Z