Gitea: Unintended Proxy or Intermediary ('Confused Deputy') (CVE-2026-94205)
Published Last modified Sources: BSI
What is affected, what to do
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.
Update gitea to version 28.1.0, Gitea to version 28.0.0.
- Affected
- Gitea
lte *..1.27.3
- Gitea
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: BSI
0.6 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 50.0
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 70.03 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.6 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 50.0
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 7 October 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-441, CWE-863
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Gitea | Gitea |
|
|
| gitea | gitea |
|
|
| Open Source | Gitea |
|
|
Distribution and container packages (3)
Downstream packages (e.g. Bitnami, Debian, Ubuntu, Red Hat). Versions refer to the distribution, not the vendor.
| Affected versions | Fixed in | ||
|---|---|---|---|
| bitnami | gitea |
|
|
Vendors and products
Weakness classes (CWE)
CWE-441Unintended Proxy or Intermediary ('Confused Deputy')
Class
The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor.
Entry at MITRE CWE-441CWE-863Incorrect Authorization
Class
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Entry at MITRE CWE-863
References & sources
- github.comGitHub Security Advisory GHSA-94rx-fqm6-q23vVendor advisory
- github.comFix: go-gitea/gitea pull request #39501Patch
- github.comFix backport to release/v28: go-gitea/gitea pull request #39507Patch
- blog.gitea.comGitea 28.1.0 release announcementRelease notes
- github.comgo-gitea/gitea v28.1.0 releaseRelease notes
- NVD (NIST)vuln/detail/CVE-2026-96594web
- github.comGitHub Security Advisory GHSA-pvjf-7jrm-6w9gVendor advisory
- github.comFix: go-gitea/gitea pull request #39399Patch
- blog.gitea.comGitea 28.0.0 release announcementRelease notes
- github.comgo-gitea/gitea v28.0.0 releaseRelease notes
- NVD (NIST)vuln/detail/CVE-2026-104632web
- github.comGitHub Security Advisory GHSA-6pv5-8rp7-8c75Vendor advisory
- github.comFix: go-gitea/gitea pull request #39472Patch
- NVD (NIST)vuln/detail/CVE-2026-95106web
- github.comGitHub Security Advisory GHSA-xh39-mxw9-34ppVendor advisory
- NVD (NIST)vuln/detail/CVE-2026-94205web
- github.comGitHub Security Advisory GHSA-7769-9pr9-m24hVendor advisory
- github.comFix: go-gitea/gitea pull request #37306Patch
- NVD (NIST)vuln/detail/CVE-2026-79960web
- github.comGitHub Security Advisory GHSA-7v5j-mph8-9w6gVendor advisory
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Gitea (before 28.0.0)
Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Product configuration added —OR *cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:* versions up to (excluding) 28.0.0Reference type added —Gitea Limited: https://blog.gitea.com/release-of-28.0.0/ Types: Release NotesReference type added —Gitea Limited: https://github.com/go-gitea/gitea/pull/39399 Types: PatchReference type added —Gitea Limited: https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Types: Release NotesReference type added —Gitea Limited: https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp Types: Exploit, Mitigation, Vendor AdvisorySource identifier: nvd@nist.gov
Record modifiedCISA ADP
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSSVC assessment added —{"id":"CVE-2026-94205","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-07T20:11:31.504995Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedGitea
Weakness type: CWE-441, CWE-863
Description added or changed
Show 8 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.Weakness type (CWE) added —CWE-441Weakness type (CWE) added —CWE-863Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/94xxx/CVE-2026-94205.json">CVE-2026-94205</a>Reference added —https://blog.gitea.com/release-of-28.0.0/Reference added —https://github.com/go-gitea/gitea/pull/39399Reference added —https://github.com/go-gitea/gitea/releases/tag/v28.0.0Reference added —https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34ppSource identifier: 88ee5874-cf24-4952-aea0-31affedb7ff2
Linked CVEs
| Medium | CVE-2026-97626 | Gitea profile feed disclosure bypassing user visibility | 4.3 | — |
| Medium | CVE-2026-97208 | Gitea push mirror API bypass of DISABLE_NEW_PUSH policy | 4.9 | — |
| Medium | CVE-2026-96594 | Gitea repository media API stored XSS | 6.1 | — |
| Medium | CVE-2026-96589 | Gitea private repository access retained after rejected transfer | 4.3 | — |
| High | CVE-2026-96580 | Gitea Actions memory exhaustion through large static matrices | 7.5 | — |
| High | CVE-2026-96404 | Gitea installer authentication bypass for existing accounts | 8.1 | — |
| Medium | CVE-2026-96400 | Gitea migration SSRF to reserved addresses through ALLOWED_DOMAINS | 4.3 | — |
| High | CVE-2026-96399 | Gitea denial of service through external issue tracker patterns | 7.5 | — |
| Medium | CVE-2026-95112 | Gitea issue reference parsing CPU exhaustion | 6.5 | — |
| Critical | CVE-2026-95106 | Gitea review and execution mismatch through duplicate tree entries | 9.1 | — |
| Critical | CVE-2026-94205 | Gitea fork workflow approval bypass through maintainer-triggered events | 9.8 | — |
| High | CVE-2026-89430 | Gitea push mirror SSRF and forced writes to internal Git hosts | 8.1 | — |
| Medium | CVE-2026-89182 | Gitea push-to-create bypass of FORCE_PRIVATE policy | 5.4 | — |
| High | CVE-2026-86684 | Gitea push mirror local path check uses the repository owner | 7.1 | — |
| High | CVE-2026-79960 | Gitea deploy key pushes acting as the repository owner | 7.1 | — |
| High | CVE-2026-70357 | Gitea repository migration SSRF through DNS rebinding | 7.5 | — |
| Medium | CVE-2026-105268 | Gitea issue attachment API allows changing comment attachments | 4.3 | — |
| High | CVE-2026-105267 | Gitea tag delete route deletes releases without release permission | 8.1 | — |
| High | CVE-2026-104636 | Gitea SSRF through Git HTTP redirects in mirrors and fetches | 7.5 | — |
| Medium | CVE-2026-104633 | Gitea migration memory exhaustion from zero page size | 6.5 | — |
| High | CVE-2026-104632 | Gitea fork workflow approval bypass through cancel and rerun | 8.8 | — |
| High | CVE-2026-104626 | Gitea fork workflow job revival through later approval | 8.8 | — |
| High | CVE-2026-103670 | Gitea trusted workflow cancellation by unapproved fork runs | 7.5 | — |
| Medium | CVE-2026-103667 | Gitea container registry stored XSS through blob media type | 5.4 | — |
Show 5 more CVEs
| High | CVE-2026-103504 | Gitea API team demotion not applied to unit permissions | 8.1 | — |
| Critical | CVE-2026-103059 | Gitea built-in SSH server authentication bypass through key case folding | 9.1 | — |
| Medium | CVE-2026-101029 | Gitea migration and pull mirror SSRF through multi-answer DNS | 4.3 | — |
| High | CVE-2026-101027 | Gitea migration SSRF through ALLOWED_DOMAINS address check bypass | 7.7 | — |
| Critical | CVE-2026-101023 | Gitea OAuth2 refresh token grant accepts access tokens | 9.1 | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-94205"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-94205.svg?lang=en" alt="CVE-2026-94205 – NEOSEC Intel" height="20"></a>