CVE-2026-129341: Gitea release asset deletion by former writers
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Fixed version: Gitea Gitea 28.4.0.
Low priority for now. Upgrade to Gitea Gitea 28.4.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
The web endpoint that removes an attachment skipped the permission check when the request came from the user who had uploaded the attachment, and it was reachable with read access to issues or pull requests. A user who had uploaded a release asset could still delete it after losing write access to the repository. The endpoint now only deletes attachments that the user uploaded and that are not yet linked to an issue, comment or release.
- Published
- Nov 15, 2026
- Updated
- Nov 15, 2026
- EPSS
- —
- CWE
- CWE-863
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · —
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.
Gitea Gitea
- 1.11.0 and later · before 28.4.0affected · semver
Same product
gitea: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-60004Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.KEV76This week
- CVE-2026-59774Gitea Org-mode file disclosure and code execution60This week
- CVE-2022-30781Gitea before 1.16.7 does not escape git fetch remote.60This week
Published before and after this one in the same product
- ← EarlierCVE-2026-128365Nov 15, 2026 · Gitea required approval bypass through team review request removal0Monitor
- ← EarlierCVE-2026-129337Nov 15, 2026 · Gitea push without write access to repositories still being created0Monitor
- Later →CVE-2026-129525Nov 15, 2026 · Gitea pull request disclosure to members with access to issues only0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Gitea Gitea | 28.4.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 16, 2026same day
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- https://github.com/silverwindremediation developer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-11628914 days apartGitea public-only token bypass through Actions runner registration36Monitor
- CVE-2026-11768514 days apartGitea public-only package token access to private OCI blobs36Monitor
- CVE-2026-7118432 days apartGitea fork workflow approval bypass through review events35Monitor
- CVE-2026-11944114 days apartGitea public-only token bypass on bulk organization repository deletion30Monitor
- CVE-2026-7996040 days apartGitea deploy key pushes acting as the repository owner28Monitor
- CVE-2026-8668440 days apartGitea push mirror local path check uses the repository owner28Monitor
Not on record for this CVE: EPSS history · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationAttack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.