Gitea Open Source Git Server · Vulnerability
cve-program · CVE-2026-58438
PublishedCross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
Read the publisher's advisoryeuvd · EUVD-2026-58165
PublishedCross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
Read the publisher's advisorynvd · CVE-2026-58438
PublishedCross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access
Read the publisher's advisoryosv · GHSA-xv9x-fj9g-vj6h
Published### Details `RemoveDependency` in `routers/web/repo/issue_dependency.go` takes a `removeDependencyID` form parameter identifying the other issue by its global numeric ID, and fetches it with `issues_model.GetIssueByID(ctx, depID)` - no repository or permission check at all. It then calls `issues_model.RemoveIssueDependency(ctx, ctx.Doer, issue, dep, depType)` (`models/issues/dependency.go`), which deletes the dependency join row and then writes a comment referencing the removal, attributed to the calling user, onto the dependency record. The sibling function in the very same file, `AddDependency`, does this correctly when the two issues are in different repos (which `ALLOW_CROSS_REPOSITORY_DEPENDENCIES`, on by default, permits): ```go if issue.RepoID != dep.RepoID { if !setting.Service.AllowCrossRepositoryDependencies { ... } depRepoPerm, err := access_model.GetDoerRepoPermission(ctx, dep.Repo, ctx.Doer) if !depRepoPerm.CanReadIssuesOrPulls(dep.IsPull) { return // you can't see this dependency } } ``` `RemoveDependency` has no equivalent block at all - it goes straight from resolving `dep` by ID to deleting the link, regardless of which repo `dep` lives in or whether the caller can see it. I confirmed this same code is present in the current latest release, v1.26.4. ### PoC Prerequisites: an account with write access to issues on some repo `ownerA/repoA`, and the global numeric issue ID of an issue in a private repo `repoB` that is (or was) legitimately dependency-linked to one of the attacker's issues in `repoA` (cross-repo dependencies are commonly used between related public/private repos, and `ALLOW_CROSS_REPOSITORY_DEPENDENCIES` defaults to enabled). ```bash curl -s -b "gitea_session=$ATTACKER_SESSION_COOKIE" -X POST \ --data-urlencode "removeDependencyID=<repoB_issue_global_id>" \ --data-urlencode "dependencyType=blockedBy" \ "https://TARGET_HOST/ownerA/repoA/issues/N/dependency/delete" # Expected: the dependency link is deleted and a "removed dependency" comment # authored by the attacker is added to the repoB issue, even though the # attacker has no read access to repoB. ``` ### Impact This is a cross-repository IDOR / broken access control issue. An attacker can tamper with issue-tracking state (dependency relationships) and inject an attacker-authored comment into a private repository they cannot otherwise read or write to, crossing a trust boundary the "add" path explicitly enforces. Impact is bounded - it requires an existing dependency link and discloses no repository content - but it is a genuine unauthorized-write primitive across a private-repo boundary. ### Fix Add the same cross-repo permission check used in `AddDependency` (`access_model.GetDoerRepoPermission(ctx, dep.Repo, ctx.Doer).CanReadIssuesOrPulls(dep.IsPull)`) to `RemoveDependency` before allowing the deletion to proceed when `issue.RepoID != dep.RepoID`. **If possible, please apply for a CVE number when publishing. I would greatly appreciate it.**
Read the publisher's advisoryosv · GO-2026-6085
PublishedGitea: Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access in gitea.dev
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-58438 · CVE overview and exploitation status
cve-program · CVE-2026-58438
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xv9x-fj9g-vj6h
- https://github.com/go-gitea/gitea/releases/tag/v1.27.0
- https://blog.gitea.com/gitea-1.27.0-is-released/
euvd · EUVD-2026-58165
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xv9x-fj9g-vj6h
- https://github.com/go-gitea/gitea/releases/tag/v1.27.0
- https://blog.gitea.com/gitea-1.27.0-is-released/
nvd · CVE-2026-58438
- https://blog.gitea.com/gitea-1.27.0-is-released/
- https://github.com/go-gitea/gitea/releases/tag/v1.27.0
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xv9x-fj9g-vj6h
osv · GHSA-xv9x-fj9g-vj6h
- https://github.com/go-gitea/gitea/security/advisories/GHSA-xv9x-fj9g-vj6h
- https://github.com/go-gitea/gitea
- https://github.com/go-gitea/gitea/releases/tag/v1.27.0
osv · GO-2026-6085
Related changes
Linked by CVE identifier- Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access · Advisory content revised · 15 Nov 2026