FKIE_CVE-2026-94205
Vulnerability from fkie_nvd - Published: 2026-10-06 20:17 - Updated: 2026-10-06 20:17
Severity
Summary
Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository's runners without an explicit approval.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"packageName": "gitea.dev",
"product": "Gitea",
"vendor": "Gitea",
"versions": [
{
"lessThanOrEqual": "1.27.3",
"status": "affected",
"version": "0",
"versionType": "semver"
}
]
}
],
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather than the pull request author. For `pull_request` activity triggered by a maintainer during ordinary triage, such as adding a label, the run was created without requiring approval, while the workflow definition was still taken from the fork head. Where Actions is enabled and a matching runner is registered, fork-controlled workflow code could run on the base repository\u0027s runners without an explicit approval."
}
],
"id": "CVE-2026-94205",
"lastModified": "2026-10-06T20:17:34.733",
"metrics": {},
"published": "2026-10-06T20:17:34.733",
"references": [
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://blog.gitea.com/release-of-28.0.0/"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/pull/39399"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/releases/tag/v28.0.0"
},
{
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-xh39-mxw9-34pp"
}
],
"sourceIdentifier": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-441"
},
{
"lang": "en",
"value": "CWE-863"
}
],
"source": "88ee5874-cf24-4952-aea0-31affedb7ff2",
"type": "Secondary"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…