Finding and attribution
When RequireSigninView is disabled (the default), Gogs issue and release attachment upload routes were in a router group that allowed anonymous access. A remote user could obtain a same-origin CSRF token and upload arbitrary files, allowing public content hosting and repeated-upload disk exhaustion.
Product: Gogs. AI system: GPT-5. Team / organization: OpenAI Security Research / Gogs maintainers.
CVE identifiers: CVE-2026-25242.
AI and human contribution (source account): The Gogs advisory embeds an OpenAI Security Research report naming OpenAI as discoverer and gives the case-specific timeline “Discovered via GPT5” followed by PoC reproduction and confirmation. The report does not establish autonomous discovery or a more detailed model workflow.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The public maintainer advisory was published 2026-02-14. The report documents a reproduced proof of concept; it does not report exploitation in the wild or establish whether defenders knew of the flaw before discovery.
Remediation status: fix documented. PR #8128 moves /issues/attachments and /releases/attachments from ignSignIn to reqSignIn. The upstream commit is 628216d5889fcb838c471f4754f09b935d9cd9f3. The repository advisory lists 0.14.0 as patched; GitHub Advisory Database now lists <0.14.1 affected and 0.14.1 patched, and repository releases include 0.14.1. The corrected current boundary is retained; installed patch state is not established.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 14 Feb 2026. AI attribution dated 14 Feb 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Not available · no assessment established here. Documented technical effects: data modification, denial of service.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
No source-backed CVSS assessment is established in this catalog.
CVE-2026-25242: data modification, denial of service.
Prerequisites / affected scope: When RequireSigninView is disabled, which the report identifies as the default, anonymous remote users can obtain a CSRF token from the homepage and upload to /issues/attachments or /releases/attachments. Arbitrary file content is stored; repeated uploads can exhaust disk space..
Exploitation evidence: The embedded report includes a proof of concept; it does not report exploitation in the wild.. Impact source · checked 17 Nov 2026.
Documented fix: PR #8128 moves /issues/attachments and /releases/attachments from ignSignIn to reqSignIn. The upstream commit is 628216d5889fcb838c471f4754f09b935d9cd9f3. The repository advisory lists 0.14.0 as patched; GitHub Advisory Database now lists <0.14.1 affected and 0.14.1 patched, and repository releases include 0.14.1. The corrected current boundary is retained; installed patch state is not established.