Gitea improperly exposes issue titles and repository names through previously started stopwatches

Description

References

• nvd.nist.gov/vuln/detail/CVE-2026-20883 · ADVISORY
• go-gitea/gitea#36340 · WEB
• go-gitea/gitea#36368 · WEB
• go-gitea/gitea commit 95ea2df · WEB
• blog.gitea.com/release-of-1.25.4 · WEB
• go-gitea/gitea release v1.25.4 · WEB
• pkg.go.dev/github.com/go-gitea/gitea · PACKAGE
• blog.gitea.com/release-of-1.25.4 · Release Notes
• go-gitea/gitea security advisory · Broken Link
• GitHub Advisory GHSA-j8xr-c56q-m8jj · ADVISORY

Altre vulnerabilità di code.gitea.io/gitea

• CVE-2026-59766MEDIO 4.3Gitea's starred-repository and tracked-time API endpoints do not re-check current repository permissions before returning data associated wi…
• CVE-2026-60004CRITICO 9.8EXPLOITED (CISA KEV)Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
• CVE-2026-59763MEDIO 4.3Unbounded Arch package file metadata can cause resource amplification in Gitea package uploads
• CVE-2026-58511BASSO 2.7Webhook Authorization Header Returned in Plaintext via API
• CVE-2026-58510MEDIO 4.3GHSA-8fwc-qjw5-rvgp ClearRepoWatches fix not applied to API EditRepo path — sister code path retains stale watches on public->private