Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Gitea/Gitea Open Source Git Server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Gitea/Gitea Open Source Git Server.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 13, 2026

Sources and claim methodology

• Source referenceblog.gitea.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• Gitea runner registration-token GET endpoint performs a write under a read-only token scopeSame gitea/gitea open source git server package
• Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routesSame gitea/gitea open source git server package
• Gitea Remember-Me Token Theft Not Invalidating Attacker SessionSame gitea/gitea open source git server package
• Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package UploadSame gitea/gitea open source git server package
• Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository ExfiltrationSame gitea/gitea open source git server package
• Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIsSame gitea/gitea open source git server package

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Gitea/Gitea Open Source Git Server (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Gitea/Gitea Open Source Git Server.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 13, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 13, 2026

Sources and claim methodology

• Source referenceblog.gitea.com
• GitHub security advisorygithub.com
• GitHub security advisorygithub.com

Related CVEs

• Gitea runner registration-token GET endpoint performs a write under a read-only token scopeSame gitea/gitea open source git server package
• Public-only tokens bypass private-resource restrictions on `/api/v1/user` self routesSame gitea/gitea open source git server package
• Gitea Remember-Me Token Theft Not Invalidating Attacker SessionSame gitea/gitea open source git server package
• Denial of Service (CPU & Memory Exhaustion) via O(N^2) String Concatenation in Debian Package UploadSame gitea/gitea open source git server package
• Repository Migration Follows Git HTTP Redirects After URL Allow/Block Validation, Enabling Internal Git Repository ExfiltrationSame gitea/gitea open source git server package
• Cross-Repo Information Disclosure via Org-Level Actions Run/Job APIsSame gitea/gitea open source git server package