Quick answers
- Is CVE-2026-117685 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117685 being exploited in the wild.
- How severe is CVE-2026-117685?
- Informational severity, published 1 November 2026.
- Which products and versions are affected?
- Gitea before 28.3.0.
- Is there a fix for CVE-2026-117685?
- Yes: fixed in Gitea 28.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117685 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-117685?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.3.0
Technical details
The vulnerability occurs in OCI cross-repository blob mount operations where the source blob was checked against the token owner's full account permissions instead of the token's restricted scope. A public-only token with write:package scope could exploit this to mount a blob from a private package (readable by the owner) into a public package (writable by the token), bypassing token scope restrictions. The private blob then becomes accessible to unauthenticated users through the public package endpoint.
Affected products
- Gitea Gitea before 28.3.0
Timeline
- 2026-11-01: disclosed
- 2026-11-01: patched: fixed in Gitea 28.3.0 via PR #39690 and #39853