How severe is CVE-2026-104626?

CVE-2026-104626 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-104626 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-104626?

CVE-2026-104626 affects Gitea. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-104626?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-104626 published?

CVE-2026-104626 was published on 2026-10-06 and last updated on 2026-10-13.

CVE-2026-104626

CVE-2026-104626 is a high-severity vulnerability in Gitea with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-841.

Key facts

Severity: High (CVSS 3.x base score 8.8)
EPSS exploit prediction: 0% (25th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-841
Affected product: Gitea
Published: 2026-10-06
Last modified: 2026-10-13

Description

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.

Frequently asked questions

What is CVE-2026-104626?: 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.
How severe is CVE-2026-104626?: CVE-2026-104626 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-104626 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (25th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-104626?: CVE-2026-104626 affects Gitea. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-104626?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-104626 published?: CVE-2026-104626 was published on 2026-10-06 and last updated on 2026-10-13.

References

Affected products (1)

cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*

More vulnerabilities in Gitea

CVE-2026-94205 — Critical (CVSS 9.8): Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather…
CVE-2026-73278 — Critical (CVSS 9.8): Gitea's OAuth2 and OpenID Connect sign-in paths do not require a WebAuthn challenge when WebAuthn is the account's only…
CVE-2026-60004 — Critical (CVSS 9.8): Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
CVE-2022-42968 — Critical (CVSS 9.8): Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
CVE-2021-45331 — Critical (CVSS 9.8): An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges.…
CVE-2021-45330 — Critical (CVSS 9.8): An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies…

All CVEs affecting Gitea →

Other CWE-841 vulnerabilities

CVE-2026-3130 — Critical (CVSS 9.8): Improper Enforcement of Behavioral Controls in Devolutions Server 2025.3.15 and earlier allows an authenticated…
CVE-2025-48481 — Critical (CVSS 9.8): FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, an attacker with an unactivated…
CVE-2022-2105 — Critical (CVSS 9.4): Client-side JavaScript controls may be bypassed to change user credentials and permissions without authentication,…
CVE-2026-34582 — Critical (CVSS 9.1): Botan is a C++ cryptography library. Prior to version 3.11.1, the TLS 1.3 implementation allowed ApplicationData…
CVE-2026-95369 — High (CVSS 8.8): Inappropriate implementation in XML in Google Chrome prior to 154.0.8037.57 allowed a remote attacker to potentially…
CVE-2025-48476 — High (CVSS 8.8): FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, when adding and editing user…

Browse all CWE-841 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE:

117.24.243.99 (ipv4-addr)