Vulnerability from bitnami_vulndb
The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with [security] IMPORT_LOCAL_PATHS = true, a repository administrator who is not allowed to import local paths could add a push mirror to a local path on the server when the repository owner has that permission. Gitea then pushed the repository's refs into an existing Git repository at that path with the permissions of the Gitea process.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "gitea",
"purl": "pkg:bitnami/gitea"
},
"ranges": [
{
"events": [
{
"introduced": "1.18.0"
},
{
"fixed": "28.1.0"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2026-86684"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*"
],
"severity": "High"
},
"details": "The Gitea push mirror API checked whether the repository owner, instead of the requesting user, may use local file system paths. On instances with `[security] IMPORT_LOCAL_PATHS = true`, a repository administrator who is not allowed to import local paths could add a push mirror to a local path on the server when the repository owner has that permission. Gitea then pushed the repository\u0027s refs into an existing Git repository at that path with the permissions of the Gitea process.",
"id": "BIT-gitea-2026-86684",
"modified": "2026-10-14T09:12:20.145Z",
"published": "2026-10-14T08:43:03.580Z",
"references": [
{
"type": "ARTICLE",
"url": "https://blog.gitea.com/release-of-28.1.0/"
},
{
"type": "FIX",
"url": "https://github.com/go-gitea/gitea/pull/39501"
},
{
"type": "FIX",
"url": "https://github.com/go-gitea/gitea/pull/39507"
},
{
"type": "ARTICLE",
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.1.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-7v5j-mph8-9w6g"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86684"
}
],
"schema_version": "1.6.2",
"summary": "Gitea push mirror local path check uses the repository owner"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.