VulnerabilityPublished 15 Nov 2026

CVE-2026-129525: Gitea · Missing Authorization

Affects GiteaSource CVE Database V5

Compare

Not known to be exploited : upgrade to 28.4.0 when convenient.

Data as of 15 Nov 2026, 21:34 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 28.4.0

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Gitea to 28.4.0.

Affected software

Product	Affected	Fixed in
Giteagitea.dev	Affected <28.4.0	Fixed in 28.4.0

AI-suggested

Upgrade Gitea to version 28.4.0 or later, where the vulnerability has been fully fixed. Versions 28.2.0 and 28.3.0 contain partial fixes for the API endpoints, but the complete fix including search and milestone pages is in 28.4.0. No other mitigation is required once updated.

Description

CVE-2026-129525 is a missing authorization vulnerability in Gitea affecting several API endpoints related to issues and pull requests. The flaw allowed users with read access to either issues or pull requests, but not both, to access data from the other type through issue sub-resources and repository pages. This improper access was corrected by adding read access checks specific to the item type. The vulnerability was fixed in Gitea versions 28.2.0, 28.3.0, and fully resolved in 28.4.0.

Impact

Unauthorized users could read data from pull requests or issues they were not authorized to access, potentially exposing sensitive project information. The exposure includes metadata and content accessible via API sub-resources and repository pages. There is no indication of active exploitation in the wild.

Summary

This vulnerability in Gitea involves missing authorization checks on API endpoints that handle both issues and pull requests. Users with read permissions on issues but not pull requests could access pull request data via issue-related API sub-resources such as timeline, attachments, labels, subscriptions, tracked times, and reactions. Similarly, users with pull request read access but not issue read access could access issue data. The problem was that the endpoints did not verify which type of item was being accessed, leading to unauthorized data exposure. The issue was fixed by implementing proper read access checks for the specific unit (issue or pull request) the item belongs to. The API fixes were introduced in versions 28.2.0 and 28.3.0, with the search and milestone page fixes completed in 28.4.0.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Nov 2026, 21:34 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats