[GHSA-263q-5cv3-xq9g] code.gitea.io/gitea: add the patched version 1.23.0 - #9378
Open
zyl71 wants to merge 1 commit into
Open
[GHSA-263q-5cv3-xq9g] code.gitea.io/gitea: add the patched version 1.23.0#9378zyl71 wants to merge 1 commit into
zyl71 wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
zyl71/advisory-improvement-9378
September 7, 2026 04:28
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates
Comments
Current record: Go:code.gitea.io/gitea: introduced=0
Proposed: Go:code.gitea.io/gitea: introduced=0 fixed=1.23.0
The record has no fixed event even though the advisory text itself says 'before 1.23.0'. PR #32151 (merge commit 7adc4717) is an ancestor of tag v1.23.0 (compare API: behind, ahead_by 0) and is listed in the v1.23.0 release notes under SECURITY; the module version v1.23.0 exists on proxy.golang.org (2025-01-09). The fix was never backported to release/v1.22 (v1.22.6 diverged, ahead_by 627; no commits to the fixed files on that branch; no backport PR), so the single range 0 -> 1.23.0 is complete.
Release lines: Fix merged to main 2024-11-06 (PR #32151, milestone 1.23.0). Lines with releases around the fix: 1.22 (1.22.0 2024-05-27 .. 1.22.6 2024-12-13) - compare v1.22.6...7adc4717 is 'diverged' (ahead_by 627) and no commit on release/v1.22 touched services/attachment/attachment.go, routers/api/v1/repo/{issue,release}_attachment.go or services/context/upload/upload.go after 2024-09-01, and the PR search finds no backport PR, so the 1.22 line never received the fix and stays entirely inside 0->1.23.0. 1.23 line: v1.23.0-rc0 (2024-12-17) and v1.23.0 (2025-01-09) both contain the fix (compare 'behind', ahead_by 0); first final release is 1.23.0. 1.24/1.25/1.26 descend from main after the fix.
Maintainer statements: Advisory text: 'Gitea before 1.23.0 allows ...'; v1.23.0 release notes list #32151 under SECURITY; the blog post release-of-1.23.0 is referenced. Agrees with fixed=1.23.0. The current record only has a database_specific last_known_affected_version_range '< 1.23.0' but no fixed event.
Evidence:
Version checks:
This comes from a systematic comparison of advisory ranges with fix commits and published registry artifacts. Happy to adjust if the maintainers intend otherwise.