Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-27771Published 2026-07-03

CVE-2026-27771 — Gitea Open Source Git Server

highPublic exploit1 PoC repoNuclei template

As of 2026-07-07, CVE-2026-27771 is a HIGH-severity vulnerability in Gitea Open Source Git Server, CVSS v3.1 8.2, EPSS 1.3% (71.5th percentile). Threadlinqs Intelligence links 2 tracked threat campaigns to CVE-2026-27771, most recently “Threat Actors Mass-Probe Gitea Docker Deployments for CVE-2026-20896 Authentication Bypass Amid Exploitarium Zero-Day Leak Wave”.

CVSS v3.1
8.2/10High
EPSS
1.3%Higher than 71.5% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
2Campaigns referencing it
Priority
9.5/10Threadlinqs triage score
Published
Updated 2026-07-07
CVSS v3.1 8.2 (HIGH) · EPSS 1.3% (higher than 71.5% of all scored CVEs) · Priority 9.5/10 · Published 2026-07-03

Last updated:

What is CVE-2026-27771?

CVE-2026-27771 is an access-control / authorization flaw in the built-in package and container (OCI) registry of Gitea (and the Forgejo fork). When a repository or package was marked "private," the registry-side permission check was missing or bypassable, so the OCI Distribution Spec endpoints continued to serve image manifests and layers (and package source content) to unauthenticated/anonymous requests. As a result, any unauthenticated remote attacker could pull private container images and package artifacts using standard Docker/OCI pull commands without an account, token, or prior access. The flaw existed for roughly four years and is estimated to have affected ~30,000+ internet-facing instances across 30+ countries (concentrations in China, the U.S., Germany, France, and the U.K.). It was discovered by NoScope and responsibly disclosed to Gitea maintainers. Affected: Gitea versions prior to 1.26.2 (and equivalent Forgejo builds). Fixed in Gitea v1.26.2 via PR #37610, which adds the private/internal package label and fixes the package-source permission check.

The record classifies CVE-2026-27771 under weakness class CWE-862. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 121 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.2 — HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
EPSS (FIRST)
1.3% probability of exploitation in the next 30 days, higher than 71.5% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
9.5/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-03, last modified 2026-07-07

Is CVE-2026-27771 being exploited?

Weaponised exploit code for CVE-2026-27771 is publicly available. 1 public proof-of-concept repository is tracked for this identifier. A ProjectDiscovery Nuclei detection template exists (http/cves/2026/CVE-2026-27771.yaml). It currently carries a trending score of 38 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Gitea: Open Source Git Server

How to fix CVE-2026-27771

No vendor patch reference has been recorded for CVE-2026-27771 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-27771

2 tracked threats in the Threadlinqs corpus reference CVE-2026-27771, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, NVD, FIRST EPSS, public proof-of-concept repositories, ProjectDiscovery Nuclei. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references