Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-27761: CWE-863 in Gitea Gitea Open Source Git Server

0
Medium
VulnerabilityCVE-2026-27761cvecve-2026-27761cwe-863
Published: 07/03/2026 (07/03/2026, 20:19:36 UTC)
Source: CVE Database V5
Vendor/Project: Gitea
Product: Gitea Open Source Git Server

Description

Gitea versions up to and including 1.26.2 have a vulnerability where repository RSS and Atom feed endpoints bypass API access token scope checks. This allows tokens without the required repository scope to access private repository commit data. The vulnerability is identified as CWE-863 and has a CVSS score of 4.3, indicating medium severity.

CVSS v3.1

Score 4.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected software

GitHub Actionsmore threats →ai
go-gitea/gitea
pkg:github/go-gitea/gitea
Affected versions
<=1.26.2

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/03/2026, 21:02:19 UTC

Technical Analysis

CVE-2026-27761 affects Gitea Open Source Git Server versions up to and including 1.26.2. The issue is that repository RSS and Atom feed endpoints do not properly enforce API access token scope checks, permitting tokens lacking the necessary repository scope to retrieve private repository commit information. This represents an authorization bypass vulnerability classified under CWE-863 (Incorrect Authorization). No official remediation or patch information is currently provided by the vendor, and no known exploits are reported in the wild.

Potential Impact

The vulnerability allows unauthorized access to private repository commit data via RSS and Atom feed endpoints when using API tokens without the required repository scope. This could lead to unintended exposure of sensitive commit information. There is no indication of impact on integrity or availability, only confidentiality is affected to a limited extent.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict usage of API tokens with limited scopes on affected Gitea instances and consider disabling RSS and Atom feed endpoints for private repositories if possible.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Gitea
Date Reserved
2026-03-03T03:26:00.375Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a4820fe27e9c79719acc06b

Added to database: 07/03/2026, 20:52:14 UTC

Last enriched: 07/03/2026, 21:02:19 UTC

Last updated: 07/04/2026, 01:36:48 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses