Vulnerability from bitnami_vulndb
Published
2026-10-14 08:42
Modified
2026-10-14 09:12
Summary
Gitea fork workflow job revival through later approval
Details

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 later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer's later approval action, Actions to be enabled, and a runner that accepts the repository's jobs.

To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Bitnami",
        "name": "gitea",
        "purl": "pkg:bitnami/gitea"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "28.0.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "severity": [
        {
          "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
          "type": "CVSS_V3"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-104626"
  ],
  "database_specific": {
    "cpes": [
      "cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
    ],
    "severity": "High"
  },
  "details": "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 later approves the run, Gitea passed the already-cancelled job back through concurrency preparation, set it to waiting, and made it claimable by a matching runner, executing fork-controlled workflow code. Exploitation requires the maintainer\u0027s later approval action, Actions to be enabled, and a runner that accepts the repository\u0027s jobs.",
  "id": "BIT-gitea-2026-104626",
  "modified": "2026-10-14T09:12:20.145Z",
  "published": "2026-10-14T08:42:37.770Z",
  "references": [
    {
      "type": "ARTICLE",
      "url": "https://blog.gitea.com/release-of-28.0.0/"
    },
    {
      "type": "FIX",
      "url": "https://github.com/go-gitea/gitea/pull/39399"
    },
    {
      "type": "ARTICLE",
      "url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-93pj-3x56-5gc2"
    },
    {
      "type": "WEB",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-104626"
    }
  ],
  "schema_version": "1.6.2",
  "summary": "Gitea fork workflow job revival through later approval"
}



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.