CVE-2026-117685None▾ SunlitThe 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…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.1%
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.
gitea.dev < 28.3.0Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-119441NoneGitea public-only token bypass on bulk organization repository deletion
CVE-2026-118394NoneGitea OAuth2 userinfo private group disclosure to public-only tokens
CVE-2026-116289NoneGitea public-only token bypass through Actions runner registration
CVE-2026-119627NoneGitea limited-visibility profile disclosure with public-only tokens
CVE-2026-119625NoneGitea user and organization feed token scope bypass
CVE-2026-118395NoneGitea public-only token bypass in repository and organization creation