Live › vulnerability › CVE-2026-97859
Go to dashboardSeven Gitea API routes under /api/v1/users/{username} skipped the middleware that checks whether the target user is visible to the caller. An authenticated user can read the followers, following list, starred and watched repositories, and public SSH and GPG keys of users they should not be able to see.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any Gitea instance where users have limited or private visibility and accounts can log in. Instances where every user is publicly visible have little to expose. The sources do not list specific deployment setups beyond the affected routes.
No product ranges from the sources yet.
gitea --version on the server and compare against the fixed versions below.1.27.3 or 28.0.0 or later, matching your release line; the fix shipped in both.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Seven Gitea API routes under /api/v1/users/{username} (followers, following, following/{target}, starred, subscriptions, keys and gpg_keys) were registered without the individualPermsChecker middleware that enforces the visibility of the target user. An authenticated user could therefore read the followers, following list, starred and watched repositories and public SSH and GPG keys of a user with limited or private visibility, whom they could not otherwise see. The issue was fixed in 1.27.3 and 28.0.0 and disclosed with 28.2.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-97859")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.