CVE-2026-94205 (GCVE-0-2026-94205)

Vulnerability from cvelistv5 – Published: 2026-10-06 19:25 – Updated: 2026-10-06 19:25
VLAI
Title
Gitea fork workflow approval bypass through maintainer-triggered events
Summary
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 `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.
Severity
No CVSS data available.
CWE
  • CWE-441 - Unintended Proxy or Intermediary ('Confused Deputy')
  • CWE-863 - Incorrect Authorization
Assigner
References
Impacted products
Vendor Product Version CPE status
Gitea Gitea Affected: 0 , ≤ 1.27.3 (semver)
guessed Create a notification for this product.
Credits
https://github.com/Michael-JRead https://github.com/bircni https://github.com/silverwind
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "gitea.dev",
          "product": "Gitea",
          "vendor": "Gitea",
          "versions": [
            {
              "lessThanOrEqual": "1.27.3",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "https://github.com/Michael-JRead"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "https://github.com/bircni"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "https://github.com/silverwind"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "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 `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository\u0027s runners without an explicit approval."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-441",
              "description": "CWE-441: Unintended Proxy or Intermediary (\u0027Confused Deputy\u0027)",
              "lang": "en",
              "type": "CWE"
            },
            {
              "cweId": "CWE-863",
              "description": "CWE-863: Incorrect Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-10-06T19:25:04.327Z",
        "orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "shortName": "Gitea"
      },
      "references": [
        {
          "name": "GitHub Security Advisory GHSA-xh39-mxw9-34pp",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp"
        },
        {
          "name": "Fix: go-gitea/gitea pull request #39399",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/39399"
        },
        {
          "name": "Gitea 28.0.0 release announcement",
          "tags": [
            "release-notes"
          ],
          "url": "https://blog.gitea.com/release-of-28.0.0/"
        },
        {
          "name": "go-gitea/gitea v28.0.0 release",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0"
        }
      ],
      "title": "Gitea fork workflow approval bypass through maintainer-triggered events"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
    "assignerShortName": "Gitea",
    "cveId": "CVE-2026-94205",
    "datePublished": "2026-10-06T19:25:04.327Z",
    "dateReserved": "2026-10-04T21:57:35.579Z",
    "dateUpdated": "2026-10-06T19:25:04.327Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "packageName": "gitea.dev",
                "product": "Gitea",
                "vendor": "Gitea",
                "versions": [
                  {
                    "lessThanOrEqual": "1.27.3",
                    "status": "affected",
                    "version": "0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "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 `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository\u0027s runners without an explicit approval."
          }
        ],
        "id": "CVE-2026-94205",
        "lastModified": "2026-10-06T20:17:34.733",
        "metrics": {},
        "published": "2026-10-06T20:17:34.733",
        "references": [
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://blog.gitea.com/release-of-28.0.0/"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/pull/39399"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp"
          }
        ],
        "sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-441"
              },
              {
                "lang": "en",
                "value": "CWE-863"
              }
            ],
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.