CVE-2026-89182: With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook

Routine

MEDIUM 5.4UPGRADE

CVE-2026-89182 is a medium-severity flaw (CVSS 5.4) affecting gitea. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.4 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 91%)
CISA exploited list	No
Weakness	CWE-863
Published	2026-10-06
Last modified	2026-10-13

Publisher (CNA): Gitea Limited · Vendor: gitea

Last updated 2026-10-13 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-10-06 22:17 UTCPublished CVE record published
2026-10-13 18:03 UTCUpdated Record last modified

gitea gitea UPGRADE

Affected: >= 1.27.0 and < 28.1.0

Fixed in: 28.1.0

Safe to downgrade to: a release before 1.27.0

1. Check installed version

apt-cache policy gitea || rpm -q gitea || gitea --version

2. UPGRADE to 28.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade gitea

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade gitea

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.27.0 (Debian / Ubuntu)

apt-cache madison gitea sudo apt install gitea=<VERSION_BEFORE_1.27.0> sudo apt-mark hold gitea

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list gitea sudo dnf downgrade gitea-<VERSION_BEFORE_1.27.0> sudo dnf versionlock add gitea

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-89182?

gitea: upgrade to 28.1.0. Exact commands for each OS are on this page.

Is CVE-2026-89182 being exploited?

CVE-2026-89182 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-89182 affect?

CVE-2026-89182 affects gitea. Severity is medium (CVSS 5.4). With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories c

How urgent is CVE-2026-89182?

Priority 21/100. No elevated risk signals yet.

Software pages

Gitea vulnerabilities

Related CVEs

CVE-2026-101027 HIGH 7.7 UPGRADE When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without ch
CVE-2026-101029 MEDIUM 4.3 UPGRADE Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns mult
CVE-2026-103059 CRITICAL 9.1 UPGRADE When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked u
CVE-2026-103667 MEDIUM 5.4 UPGRADE Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in p
CVE-2026-103670 HIGH 7.5 UPGRADE When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled

References

← Back to latest CVEs