---
id: "CVE-2026-116296"
kind: "vulnerability"
aliases: ["CVE-2026-116296"]
title: "Forge API let writers change archived repositories' releases and labels"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "other"
products: []
ecosystems: []
tags: ["api", "git-forge", "other", "self-hosted"]
not_affected_if: ["no-archived-repositories", "read-only-tokens"]
published_at: "2026-11-01T10:18:35+00:00"
first_seen_at: "2026-11-01T10:49:33+00:00"
updated_at: "2026-11-01T10:51:37+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116296", "first_seen_at": "2026-11-01T10:49:33+00:00"}]
---

# Forge API let writers change archived repositories' releases and labels

The API routes for releases, release assets, milestones and repository labels accepted changes to archived, read-only repositories. A user with write access, or a write-scoped token holder, could replace release assets, delete releases and tags, and edit milestones and labels.

_Summary, check and fix written by a model from the sources; labelled as such._

## Fix

- Changing requests on these routes now return 423 Locked for archived repositories; the sources do not name the fixed version.

## Timeline

- 2026-11-01T10:49:33+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116296

## From the sources

The API routes for releases, release assets, milestones and repository labels did not reject changes to archived repositories. A user with write access to an archived repository, or a holder of such a user's write-scoped token, could replace or delete release assets while keeping their download URLs, delete releases and tags, and create, edit or delete milestones and labels of a repository that is meant to be read-only. Changing requests on these routes now return 423 Locked for archived repositories.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_