Skip to content
Noroxi
CVE-2026-20896· NVD / CVE Program· CNA Gitea

Gitea Docker image trusts spoofable reverse-proxy headers by default

Gitea Docker image versions up to and including 1.26.2 use REVERSE_PROXY_TRUSTED_PROXIES=* by default, allowing any source IP to impersonate a user when reverse-proxy authentication headers such as X-WEBAUTH-USER are enabled.

CriticalCVSS 9.8 · v3.1—Proof of concept Fix available
Published
Jul 3, 2026
Updated
Jul 7, 2026
EPSS
2.8% · 86th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.8%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Gitea
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.

  • Gitea Gitea Open Source Git Server

    • up to and including 1.26.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gocode.gitea.io/giteabefore 1.26.31.26.3

Other highest-scoring records for the same primary product.

  • CVE-2024-6886Inproper Sanitation of field leading to stored XSS
    50Plan
  • CVE-2026-56654Privilege Escalation via Access Token Scope Escalation in API
    39Monitor
  • CVE-2026-58422Improper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts
    39Monitor
  • CVE-2026-27780Gitea pre-receive hook can miss branch-protection checks after scanner errors
    39Monitor
  • CVE-2026-26292Gitea LFS mirror synchronization bypasses migration HTTP transport restrictions
    39Monitor
  • CVE-2026-56443Token public-only scope bypassed on Limited-visibility owners (Repository + Package categories) — residual after CVE-2026-25714 / PR #37118
    38Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:code.gitea.io/gitea1.26.3Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×7

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2026-20896 —
Proof-of-concept repository on GitHubstars:12026-07-02
Proof-of-concept repository on GitHubstars:62026-07-05
Proof-of-concept repository on GitHubstars:102026-07-07
Proof-of-concept repository on GitHubstars:62026-07-16
Proof-of-concept repository on GitHubstars:12026-07-29
Proof-of-concept repository on GitHubstars:12026-08-15
Proof-of-concept repository on GitHubstars:12026-08-21

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-2 d
  2. Published
  3. TodaySep 30, 2026+89 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-262920 days apartGitea LFS mirror synchronization bypasses migration HTTP transport restrictions
    39Monitor
  • CVE-2026-584220 days apartImproper authorization on OAuth sign-in callback silently re-enables administrator-disabled accounts
    39Monitor
  • CVE-2026-5665441 days apartPrivilege Escalation via Access Token Scope Escalation in API
    39Monitor
  • CVE-2026-207060 days apartGitea repository archive downloads bypass token scope checks
    36Monitor
  • CVE-2026-262470 days apartGitea OAuth2 PKCE S256 challenges are not enforced during token exchange
    36Monitor
  • CVE-2026-5675041 days apartGitea Remember-Me Token Theft Not Invalidating Attacker Session
    36Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records