CVE-2026-117685 Gitea CVE debrief

Who should care

Defenders managing OCI registries, users with 'write:package' scope tokens, and teams responsible for package and blob security should assess exposure and verify configurations to prevent unauthorized access. This includes reviewing token scopes, restricting cross-repository blob mounts, and monitoring blob downloads to prevent unauthorized access.

Why it matters

CVE-2026-117685 allows unauthorized access to private package blobs through a vulnerability in the OCI registry's cross-repository blob mount feature. Defenders should verify configurations, restrict token scopes, and monitor blob downloads to prevent unauthorized access.

• Potential unauthorized access to private package blobs.
• Possible unintended exposure of sensitive data through public packages.
• Need for verification of OCI registry configurations and token scopes.
• Potential for increased risk if not properly mitigated.

Technical summary

The OCI registry's cross-repository blob mount feature improperly checks permissions, allowing a 'public-only' token with 'write:package' scope to mount a private blob into a public package. This vulnerability affects OCI registry configurations and requires verification of token scopes and blob security. The private blob can then be downloaded by anyone through the public package, enabling unauthorized access to private package blobs. Defenders managing OCI registries should assess exposure and verify configurations to prevent unauthorized access.

Defensive priority

Defenders should prioritize verifying exposed OCI registry configurations, reviewing token scopes, and restricting cross-repository blob mounts to prevent unauthorized access.

Recommended defensive actions

• Verify exposed OCI registry configurations and restrict cross-repository blob mounts.
• Review and restrict token scopes to prevent unauthorized access.
• Monitor for and respond to potential blob downloads from public packages.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability. Gitea's release notes and GitHub pull requests offer additional context. The vulnerability allows unauthorized access to private package blobs through a vulnerability in the OCI registry's cross-repository blob mount feature. A 'public-only' token with 'write:package' scope can mount a private blob into a public package. The private blob can then be downloaded by anyone through the public package. This vulnerability affects OCI registry configurations and requires of

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.