---
id: "CVE-2026-110324"
kind: "vulnerability"
aliases: ["CVE-2026-110324"]
title: "Gitea: private profile details leak to any signed-in user via follow"
severity: "medium"
cvss: 6.5
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["git-hosting", "gitea", "runtime", "self-hosted"]
not_affected_if: ["no-private-profiles", "patched-version"]
published_at: "2026-10-18T19:16:33+00:00"
first_seen_at: "2026-10-23T21:57:17+00:00"
updated_at: "2026-10-25T03:57:28+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110324", "first_seen_at": "2026-10-23T21:57:17+00:00"}]
---

# Gitea: private profile details leak to any signed-in user via follow

Gitea checked profile visibility only on GET requests, while POST /{username} (follow and unfollow) accepted any signed-in user. An authenticated user can read the full name, location, website and description of a user whose profile is private.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Gitea version with `gitea --version` or the running binary; versions below `28.1.0` are affected.
- Confirm whether private profiles are in use for users on the instance.

## Fix

- Upgrade Gitea to `28.1.0` or later; the sources say the fix shipped in `28.1.0` and was disclosed with `28.2.0`.

## Timeline

- 2026-10-23T21:57:17+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110324

## From the sources

The visibility check of Gitea user profiles was applied to GET requests only, while `POST /{username}` (follow and unfollow) required only a signed-in user. Any authenticated user could therefore obtain the full name, location, website and description of a user with a private profile from the response. The issue was fixed in 28.1.0 and disclosed with 28.2.0.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_