CVE-2026-58370: Authentication Bypass by Spoofing in woodpecker-ci woodpecker
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.
AI Analysis
Technical Summary
CVE-2026-58370 is an authentication bypass vulnerability affecting woodpecker-ci woodpecker versions before 3.15.0. The issue is specific to the GitLab forge driver, where the pipeline.Author is derived from the git commit author name in the webhook payload. Since this commit author name is attacker-controlled and not verified by GitLab, an attacker who can open a merge request from a fork can spoof this field to match an entry in the ApprovalAllowedUsers bypass list. This causes the needsApproval check to return false, allowing the pipeline to run without the required approval. Consequently, attacker-controlled pipeline steps can execute on a Woodpecker agent, risking exfiltration of CI secrets. Other built-in forge drivers are unaffected because they use forge-validated sender identities.
Potential Impact
The vulnerability allows an attacker who can open a merge request from a fork in GitLab to bypass the approval requirement for pipeline execution in woodpecker-ci woodpecker. This enables execution of arbitrary pipeline steps controlled by the attacker, potentially leading to unauthorized access and exfiltration of sensitive CI secrets. The impact includes confidentiality, integrity, and availability consequences as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting merge request permissions or disabling the ApprovalAllowedUsers bypass list for GitLab forge driver pipelines. Monitoring for suspicious pipeline executions and limiting exposure of sensitive secrets in CI environments may reduce risk. Verify with the woodpecker-ci project for updates or patches addressing this issue.
CVE-2026-58370: Authentication Bypass by Spoofing in woodpecker-ci woodpecker
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.
CVSS v3.1
Score 8.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-58370 is an authentication bypass vulnerability affecting woodpecker-ci woodpecker versions before 3.15.0. The issue is specific to the GitLab forge driver, where the pipeline.Author is derived from the git commit author name in the webhook payload. Since this commit author name is attacker-controlled and not verified by GitLab, an attacker who can open a merge request from a fork can spoof this field to match an entry in the ApprovalAllowedUsers bypass list. This causes the needsApproval check to return false, allowing the pipeline to run without the required approval. Consequently, attacker-controlled pipeline steps can execute on a Woodpecker agent, risking exfiltration of CI secrets. Other built-in forge drivers are unaffected because they use forge-validated sender identities.
Potential Impact
The vulnerability allows an attacker who can open a merge request from a fork in GitLab to bypass the approval requirement for pipeline execution in woodpecker-ci woodpecker. This enables execution of arbitrary pipeline steps controlled by the attacker, potentially leading to unauthorized access and exfiltration of sensitive CI secrets. The impact includes confidentiality, integrity, and availability consequences as indicated by the CVSS vector (C:H/I:H/A:H).
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider restricting merge request permissions or disabling the ApprovalAllowedUsers bypass list for GitLab forge driver pipelines. Monitoring for suspicious pipeline executions and limiting exposure of sensitive secrets in CI environments may reduce risk. Verify with the woodpecker-ci project for updates or patches addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-06-30T12:15:07.392Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a43f43127e9c79719185f9d
Added to database: 06/30/2026, 16:52:01 UTC
Last enriched: 06/30/2026, 17:06:29 UTC
Last updated: 06/30/2026, 18:00:36 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.