Gitea RSS/Atom Feed Handlers Bypass API-Token Scope Enforcement
Gitea's RSS/Atom feed handlers reportedly bypass API-token scope enforcement, potentially allowing unauthorized access to private content. Users of affected versions should monitor for updates.
What happened
An early warning has been issued regarding a potential security issue in Gitea's RSS/Atom feed handlers. The handlers appear to accept API-token Basic authentication but do not enforce token scope or public-only confinement. This could allow private content to be accessed through the feed routes, bypassing intended token confinement.
The issue is under investigation and is tracked under GHSA-6CQF-375W-639G. The affected component is Gitea (go), introduced in version 0 and reportedly fixed in version 1.27.0. Users are advised to monitor for updates from the Gitea team that address the incomplete fix of scope enforcement in feed handlers.
Professional software engineers assessing their exposure should consult the primary sources for more detailed information. The exact impact and necessary mitigations are still being determined, so staying informed through official channels is crucial.
How 0Day mitigates this
gitea is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.