CVE.org (no NVD analysis yet)· CNA Gitea

CVE-2026-59766: Gitea private repository metadata disclosure after access revocation

MediumCVSS 4.3 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: code.gitea.io/gitea (Go) 1.27.0; gitea.dev (Go) 1.27.0.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to code.gitea.io/gitea (Go) 1.27.0; gitea.dev (Go) 1.27.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated with the requesting user. A user whose access to a private repository has been revoked can still retrieve repository metadata through /api/v1/user/starred and private issue titles through /api/v1/user/times. The disclosure depends on relationships or tracked-time entries created before access was revoked.

Broken access control (IDOR)

Published: Oct 14, 2026
Updated: Oct 14, 2026
EPSS: 0.2% · 20th percentile
CWE: CWE-284

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

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
- 1.25.4affected

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Go	code.gitea.io/gitea	before 1.27.0	1.27.0
Go	gitea.dev	before 1.27.0	1.27.0

Same product

gitea: all records

Other highest-scoring records for the same primary product.

CVE-2026-60004Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.KEV
76This week
CVE-2026-59774Gitea Org-mode file disclosure and code execution
60This week
CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.
60This week

Published before and after this one in the same product

← EarlierCVE-2026-97626Oct 6, 2026 · Gitea profile feed disclosure bypassing user visibility
17Monitor
← EarlierCVE-2026-25946Oct 14, 2026 · Gitea OpenID discovery server-side request forgery
21Monitor
Later →CVE-2026-60008Oct 14, 2026 · Gitea Jupyter notebook UI redress through CSS class injection
14Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Go:code.gitea.io/gitea	1.27.0	Package registry (OSV)
Go:gitea.dev	1.27.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

PublishedOct 14, 2026
Fix recordedOct 15, 2026+1 d
TodayNov 13, 2026+30 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.

go-gitea/giteaPR 38324

Credits

All researchers

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

https://github.com/sec-reexreporter

Variant candidates

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

CVE-2026-20750265 days apartGitea Organization Projects Cross-Organization Authorization Bypass via Project ID (IDOR)
36Monitor
CVE-2026-20897265 days apartGitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)
36Monitor
CVE-2026-20912265 days apartGitea: Cross-Repository Authorization Bypass via Release Attachment Linking Leads to Private Attachment Disclosure
36Monitor
CVE-2026-668770 days apartGitea fork workflow approval bypass through concurrency cancellation
32Monitor
CVE-2026-11839518 days apartGitea public-only token bypass in repository and organization creation
30Monitor
CVE-2026-20736265 days apartGitea Web Attachment Deletion: Cross-Repository Unauthorized Deletion via Missing Repo Ownership Check
30Monitor