Gitea CVE-2025-68944

Requires an attacker to already possess a valid Gitea access token whose scope does NOT include package permissions; the flaw is that the Conan and Container (and related NuGet) package registry authentication paths failed to verify the token carried read:package/write:package/all scope before issuing a package authorization token, so a lower-scoped token was wrongly accepted. Exploitation is therefore limited to instances where package registries are in use and the attacker can present some valid token; it does not permit fully anonymous access and is bounded to package read/write operations rather than full repository or admin compromise.

This is a moderate-severity, confused-deputy token-scope flaw (CWE-441) in Gitea's package registries, and the aggregate signals point to a LOW real-world priority rather than an urgent one. EPSS is 0.28% (18th percentile) indicating low predicted exploitation, there is no CISA KEV listing (not actively exploited), and no public exploit code was identified - only the vendor fix PR (#31967) is available. The NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/C:N/I:L/A:N = 5.3) is INTERNALLY INCONSISTENT with the described defect: the vulnerability is about a scoped access token being accepted by the Conan/Container/NuGet package endpoints despite lacking the required read:package/write:package scope, so exploitation inherently requires possession of a valid (but under-scoped) Gitea token - i.e. PR should be L, not N. The PR:N rating overstates ease of attack; treat this as an authenticated scope-escalation issue, not an unauthenticated one. The source diff also shows package operations (read and write) being reachable, so the real impact plausibly touches confidentiality as well as the integrity (I:L) that NVD recorded. Net: genuine but low-urgency; patch during normal maintenance.

An attacker who already holds a legitimate Gitea personal access token scoped only for non-package operations (e.g. repository read) presents it to a package registry endpoint such as the Conan or Container API; because the token scope is not properly propagated/enforced, the under-scoped token is accepted and the attacker reads or pushes packages it should not be authorized for. No public exploit code exists, and the network attack vector with low complexity makes it trivial once any valid token is obtained.