Gitea does not properly validate repository ownership when linking attachments to releases

概要

参考情報

• nvd.nist.gov/vuln/detail/CVE-2026-20912 · ADVISORY
• go-gitea/gitea#36320 · WEB
• go-gitea/gitea#36355 · WEB
• go-gitea/gitea commit fbea2c6 · WEB
• blog.gitea.com/release-of-1.25.4 · WEB
• go-gitea/gitea · PACKAGE
• go-gitea/gitea release v1.25.4 · WEB
• blog.gitea.com/release-of-1.25.4 · Release Notes
• go-gitea/gitea security advisory · Broken Link
• access.redhat.com/security/cve/CVE-2026-20912
• bugzilla.redhat.com/show_bug.cgi
• security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-20912.json
• GitHub Advisory GHSA-4xx9-vc8v-87hv

code.gitea.io/gitea のその他の脆弱性

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