# CVE-2026-58370: Woodpecker < 3.15.0 - GitLab Approval Gate Bypass via Spoofable Commit Author Name

> Attacker bypasses approval gates by spoofing commit author names in GitLab webhooks, enabling unauthorized pipeline execution and secret exfiltration.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-wpx4-jm4h-w8j6

## What is CVE-2026-58370?

CVE-2026-58370 is a critical authentication bypass vulnerability in woodpecker-ci woodpecker, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-58370?


## How do I fix CVE-2026-58370?

No fix has been published for CVE-2026-58370 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-58370 being exploited?

There is no known exploitation of CVE-2026-58370 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-58370 and fix it if it is affected.

What it is: CVE-2026-58370 is a critical authentication bypass vulnerability in woodpecker-ci woodpecker, published on 30 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-58370 in the wild and no public exploit code.

Affected product: woodpecker-ci woodpecker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-58370/ (Markdown: https://insights.sbomify.com/CVE-2026-58370/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-58370
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-58370
- OSV: https://osv.dev/vulnerability/CVE-2026-58370

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-58370/
Summaries are generated and may contain mistakes; the official description above is the record.