CVE-2026-79960 Affecting gitea-fips-compat package, versions <28.0.0-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.21% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-GITEAFIPSCOMPAT-20948473
  • published15 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-79960  (opens in a new tab)

How to fix?

Upgrade Minimos:latest gitea-fips-compat to version 28.0.0-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitea-fips-compat package and not the gitea-fips-compat package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

When a push was authenticated with a deploy key, Gitea recorded the repository owner as the pusher, so permission checks in the push hook pipeline evaluated the owner instead of the deploy key. A holder of a writable deploy key could create protected tags without being on the tag allow list and change repository visibility through push options, for example making a private repository public. Pull requests created through the AGit flow with a deploy key were also attributed to the owner.