2504 matches found
CVE-2026-66877
Gitea is vulnerable to a workflow approval bypass where first-time fork contributor jobs can be executed without maintainer approval. The root cause is that certain job transition and dispatch paths fail to re-verify approval requirements when a separate, legitimate run sharing a job-level concur...
CVE-2026-66877 Gitea fork workflow approval bypass through concurrency cancellation
Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocked sibling jobs to be re-emitted and...
CVE-2026-66874
The Gitea repository management system is vulnerable to a bypass of required actions checks during pull request events. The root cause is that Gitea reads workflow definitions from the pull request head and automatically posts a synthetic skipped status if branch or path filters exclude execution...
CVE-2026-66874
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...
CVE-2026-66874 Gitea required Actions check bypass through skipped workflows
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...
EUVD-2026-101088
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...
CVE-2026-63792 Gitea private reusable workflow disclosure to fork runs
Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository that trusts the base repository's owner through...
CVE-2026-63792
Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository that trusts the base repository's owner through...
CVE-2026-63792
In Gitea , the CanReadWorkflowCrossRepo function fails to exclude fork pull request runs when validating cross-repository reusable workflows. Due to the collaborative-owner trust relationship, an approved fork workflow targeting a private repository can read private workflow files from another re...
BIT-GITEA-2026-96580 Gitea Actions memory exhaustion through large static matrices
Gitea expanded a workflow's static strategy.matrix into its full Cartesian product without a size limit when creating a run, before the fork pull request approval gate applied. A user who can open a pull request from a fork could submit a small workflow file whose matrix expands to a very large...
BIT-GITEA-2026-94205 Gitea fork workflow approval bypass through maintainer-triggered events
Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For pullrequest activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval,...
BIT-GITEA-2026-104632 Gitea fork workflow approval bypass through cancel and rerun
Gitea Actions blocks the jobs of workflow runs from first-time fork pull request contributors until a maintainer approves the run. The rerun path only required a run to be finished and built the new attempt's jobs without considering the pending approval, so when a user with Actions write access...
BIT-GITEA-2026-104626 Gitea fork workflow job revival through later approval
A user who can open a fork pull request can place workflow content with a shared run-level concurrency group into a Gitea Actions run that is awaiting approval. When a later run in that group cancels the blocked job, the run becomes terminal while still marked as needing approval. If a maintainer...
FreeBSD: VID-fac18f5f-afc2-11f1-8266-3c7c3fba4204 (CVE-2026-71184): Gitea -- multiple vulnerabilities
Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code from the fork hea...
CVE-2026-73800: Improper Control of Generation of Code
Gitea resolves local reusable workflow files from a fork's head commit when a trusted base-branch workflow runs for a pullrequesttarget event. A fork author can modify a referenced reusable workflow so attacker-controlled code executes with the repository and organization secrets available to tha...
CVE-2026-63792: Improper Handling of Insufficient Permissions or Privileges
Gitea's collaborative-owner authorization path for reading cross-repository reusable workflows does not exclude fork pull request runs. An approved fork workflow targeting a private repository can read workflow files from another private repository that trusts the base repository's owner through...
PT-2026-114260
Name of the Vulnerable Software and Affected Versions Gitea affected versions not specified Description The pull request review notifier fails to attach the pull request to the Actions notification. This causes the fork workflow approval gate to fail in recognizing that a run originates from a...
FreeBSD: VID-fac18f5f-afc2-11f1-8266-3c7c3fba4204 (CVE-2026-66877): Gitea -- multiple vulnerabilities
Gitea enforces first-time fork contributor approval by blocking jobs, but some job transition and dispatch paths do not re-check the run's approval requirement. A separate run sharing a job-level concurrency group can cancel a pending job and cause its blocked sibling jobs to be re-emitted and...
CVE-2026-71184: Incorrect Authorization
Gitea's pull request review notifier does not attach the pull request to the Actions notification, so the fork workflow approval gate does not recognize the run as originating from a fork. Review comment and review approval or rejection events can consequently load workflow code from the fork hea...
Unity Linux 20.1070a Security Update: libssh (UTSA-2026-130149)
The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-130149 advisory. A flaw was found in libssh. When ProxyCommand is used, an unchecked fork failure can be stored as process ID -1; during cleanup, signals may then be sent across the...