# CVE-2026-66874: Gitea required Actions check bypass through skipped workflows

> Attackers can bypass required workflow checks in Gitea by submitting fork pull requests with skipped workflows, allowing unapproved code to merge.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-5xp7-r6cr-39ff

## What is CVE-2026-66874?

CVE-2026-66874 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

For pull request events, Gitea reads workflow definitions from the pull request head and posts a synthetic skipped status when workflow branch or path filters exclude execution. A fork pull request author can supply a workflow matching a required status context but deliberately prevent it from running. Because skipped statuses count as success, branch protection or organization-required workflow checks can appear satisfied without the mandated workflow executing; no runner or maintainer approval is required for this path.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision), CWE-693 (Protection Mechanism Failure), CWE-345 (Insufficient Verification of Data Authenticity), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-66874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-66874 is a medium-severity vulnerability in Gitea, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-66874 in the wild and no public exploit code.

Affected product: Gitea. 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-66874/ (Markdown: https://insights.sbomify.com/CVE-2026-66874/index.md)
```

## Sources

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

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