Repository exposure via unchecked push visibility option
Published Oct 6, 2026 · Updated Oct 6, 2026
Repository visibility policy bypass in Gitea 1.27.0 through 28.0.0 allows remote authenticated users to make new repositories public through Git push. During push-to-create, the post-receive hook applies the client-supplied repo.private=false option after FORCE_PRIVATE has made the repository private. Exposure requires FORCE_PRIVATE and push-to-create to be enabled, plus an account permitted to create repositories; the default configuration is not affected.
Summary
What happened
Repository visibility policy bypass in Gitea 1.27.0 through 28.0.0 allows remote authenticated users to make new repositories public through Git push. During push-to-create, the post-receive hook applies the client-supplied repo.private=false option after FORCE_PRIVATE has made the repository private. Exposure requires FORCE_PRIVATE and push-to-create to be enabled, plus an account permitted to create repositories; the default configuration is not affected.
The record
- CVE
- CVE-2026-89182
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- Gitea
- Product
- Gitea
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.27.0 <=28.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started