How severe is CVE-2026-94205?

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

Is CVE-2026-94205 being actively exploited?

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

What products are affected by CVE-2026-94205?

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

How do I fix CVE-2026-94205?

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

When was CVE-2026-94205 published?

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

CVE-2026-94205

CVE-2026-94205 is a critical-severity vulnerability in Gitea with a CVSS 3.x base score of 9.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-441.

Key facts

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

Description

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.

Frequently asked questions

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

All CVEs affecting Gitea →

Other CWE-441 vulnerabilities

CVE-2026-102255 — Critical (CVSS 10.0): A Pre-authentication SSRF vulnerability exists in the SMA1000 Appliance Work Place interface due to an unintended…
CVE-2026-69399 — Critical (CVSS 10.0): Azure Arc Elevation of Privilege Vulnerability
CVE-2026-83548 — Critical (CVSS 10.0): A Pre-authentication SSRF vulnerability exists in the SMA1000 Appliance Work Place interface due to an unintended…
CVE-2026-42933 — Critical (CVSS 10.0): Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow…
CVE-2026-39906 — Critical (CVSS 10.0): Unisys WebPerfect Image Suite versions 3.0.3960.22810 and 3.0.3960.22604 expose a deprecated .NET Remoting TCP channel…
CVE-2026-100706 — Critical (CVSS 9.9): kyverno before 1.19.1 fails to properly validate URL-encoded path segments in Policy apiCall urlPath, allowing…

Browse all CWE-441 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE:

117.24.243.99 (ipv4-addr)