The Gitea web route for deleting tags (POST /{owner}/{repo}/tags/delete) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases write access could permanently delete published releases of that repository, including their attachments. Protected tag rules covering the release tag still blocked the deletion.
CVE-2026-105267
HIGHPre-NVD 8.18.1Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.1 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cisa-adp
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 8.1Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 8.1
- EG Score
- 8.1HIGHlow confidence
- EG Risk
- 36EG Risk 36/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 7, 2026
Advisory Details (5)
Auto-updated Oct 7, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
github_release Patch Available
v28.1.0
Patch available: go-gitea/gitea v28.1.0
https://github.com/go-gitea/gitea/releases/tag/v28.1.0github_pr
fix: add missing checks to several API and web handlers (#39501)
Fix merged in go-gitea/gitea PR #39507 on 2026-09-30 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39507github_pr
fix: add missing checks to several API and web handlers
Fix merged in go-gitea/gitea PR #39501 on 2026-09-30 — awaiting tagged release
https://github.com/go-gitea/gitea/pull/39501githubMentions a patch (unverified)🟡 PoC Available
POST /{owner}/{repo}/tags/delete requires only Code:Write but destroys Releases and their attachment blobs · Advisory · go-gitea/gitea · GitHub
Affected: 1.25.2, is a different route in the same area and not this.
https://github.com/go-gitea/gitea/security/advisories/GHSA-vvqw-mjq8-x248Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 20:22 UTCEG score recompute▲ 8.10
- 2026-10-07 20:21 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
- 2026-10-06 22:32 UTCNVD update
- 2026-10-06 21:47 UTCEG score recompute
- 2026-10-06 21:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-105267?
CVE-2026-105267 is a high vulnerability published on October 6, 2026. The Gitea web route for deleting tags (POST /{owner}/{repo}/tags/delete) requires only write access to the Code unit, but shares its handler with release deletion and did not check that the target was a plain tag. A collaborator with Code write access and without Releases write access could…
When was CVE-2026-105267 disclosed?
CVE-2026-105267 was first published on October 6, 2026, with the most recent update on October 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-105267?
CVE-2026-105267 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-105267?
A fix for CVE-2026-105267 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-105267
Is Your Infrastructure Affected by CVE-2026-105267?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.