Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Gitea Open Source Git Server · Vulnerability

cve-program · severity unknownEUVD CVSS 3.1 7.5 CVSS 3.1 · 134c704f-9b21-4f2e-91b3-4a467353bcc0 · Secondary 7.5 HIGHCVSS_V4 Publisher rating LOWFixed by gitea.dev 1.27.0osv · severity unknownFixed by gitea.dev 1.27.0KEV status unknown

cve-program · CVE-2026-58438

Published

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

Read the publisher's advisory

euvd · EUVD-2026-58165

Published

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

Read the publisher's advisory

nvd · CVE-2026-58438

Published

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

Read the publisher's advisory

osv · 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 advisory

osv · GO-2026-6085

Published

Gitea: 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 advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

16 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

19 Nov 2026 17:49:28 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

17 Nov 2026 17:35:17 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

15 Nov 2026 16:47:02 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

13 Nov 2026 16:01:32 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

11 Nov 2026 15:00:29 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

9 Nov 2026 14:06:49 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

7 Nov 2026 13:24:11 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

5 Nov 2026 12:41:15 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

3 Nov 2026 12:00:02 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

1 Nov 2026 11:23:09 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

30 Oct 2026 10:50:18 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

28 Oct 2026 08:36:32 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

euvd · EUVD-2026-58165 · Published

25 Oct 2026 14:19:16 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

nvd · CVE-2026-58438 · Published

24 Oct 2026 13:19:41 UTC

Gitea: Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

osv · GHSA-xv9x-fj9g-vj6h · Published

24 Oct 2026 13:19:41 UTC

Gitea: Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access in gitea.dev

osv · GO-2026-6085 · Published

23 Oct 2026 15:48:27 UTC

Cross-repository IDOR in issue-dependency removal lets an attacker tamper with and comment on private repos they cannot access

cve-program · CVE-2026-58438 · Published

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 23:16 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current