CVE-2026-118386 (GCVE-0-2026-118386)

Vulnerability from cvelistv5 – Published: 2026-11-01 09:47 – Updated: 2026-11-01 09:47
VLAI
Title
Gitea Actions fork workflow trust through pull request review commit
Summary
Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head.
Severity
No CVSS data available.
CWE
  • CWE-863 - Incorrect Authorization
Assigner
Gitea CNA under the mitre root
CNA scorecard C 61/100 over 185 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Gitea Gitea Affected: 1.19.0 , < 28.3.0 (semver)
guessed Create a notification for this product.
Credits
https://github.com/silverwind https://github.com/bircni https://github.com/wxiaoguang
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "gitea.dev",
          "product": "Gitea",
          "vendor": "Gitea",
          "versions": [
            {
              "lessThan": "28.3.0",
              "status": "affected",
              "version": "1.19.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "https://github.com/silverwind"
        },
        {
          "lang": "en",
          "type": "remediation reviewer",
          "value": "https://github.com/bircni"
        },
        {
          "lang": "en",
          "type": "remediation reviewer",
          "value": "https://github.com/wxiaoguang"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Workflows triggered by a pull request review were read from the commit named in the review\u0027s `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker\u0027s workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-863",
              "description": "CWE-863: Incorrect Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-01T09:47:07.487Z",
        "orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "shortName": "Gitea"
      },
      "references": [
        {
          "name": "GitHub Security Advisory GHSA-32h8-5xqg-h466",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h466"
        },
        {
          "name": "Fix: go-gitea/gitea pull request #40099",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40099"
        },
        {
          "name": "Fix backport to release/v28: go-gitea/gitea pull request #40117",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40117"
        },
        {
          "name": "Gitea 28.3.0 release announcement",
          "tags": [
            "release-notes"
          ],
          "url": "https://blog.gitea.com/release-of-28.3.0/"
        },
        {
          "name": "go-gitea/gitea v28.3.0 release",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/go-gitea/gitea/releases/tag/v28.3.0"
        }
      ],
      "title": "Gitea Actions fork workflow trust through pull request review commit"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
    "assignerShortName": "Gitea",
    "cveId": "CVE-2026-118386",
    "datePublished": "2026-11-01T09:47:07.487Z",
    "dateReserved": "2026-11-01T08:48:41.145Z",
    "dateUpdated": "2026-11-01T09:47:07.487Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-118386",
      "date": "2026-11-04",
      "epss": "0.00149",
      "percentile": "0.04079"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "packageName": "gitea.dev",
                "product": "Gitea",
                "vendor": "Gitea",
                "versions": [
                  {
                    "lessThan": "28.3.0",
                    "status": "affected",
                    "version": "1.19.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "Workflows triggered by a pull request review were read from the commit named in the review\u0027s `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker\u0027s workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head."
          }
        ],
        "id": "CVE-2026-118386",
        "lastModified": "2026-11-01T10:18:36.187",
        "metrics": {},
        "published": "2026-11-01T10:18:36.073",
        "references": [
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://blog.gitea.com/release-of-28.3.0/"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/pull/40099"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/pull/40117"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/releases/tag/v28.3.0"
          },
          {
            "source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
            "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-32h8-5xqg-h466"
          }
        ],
        "sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "vulnStatus": "Deferred",
        "weaknesses": [
          {
            "description": [
              {
                "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.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    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.