# CVE-2026-119627: Gitea limited-visibility profile disclosure with public-only tokens


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-5j4v-rwqr-vpq7

## What is CVE-2026-119627?

CVE-2026-119627 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026. 

### Official description

The web profile and RSS/Atom feed routes of users and organizations checked only whether a signed-in viewer could see a limited-visibility owner, without considering the `public-only` restriction of the personal access token used to authenticate. Any user holding a public-only token could send it over HTTP Basic authentication to read the profile and activity feed of limited-visibility users and organizations, which are hidden from anonymous visitors and refused on the equivalent API routes. The disclosure covers existence, profile metadata and public activity; it does not grant write access.

Weakness: CWE-1220 (Insufficient Granularity of Access Control)

## Which versions are affected by CVE-2026-119627?


## How do I fix CVE-2026-119627?

No fix has been published for CVE-2026-119627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119627 being exploited?

There is no known exploitation of CVE-2026-119627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119627 and fix it if it is affected.

What it is: CVE-2026-119627 is a medium-severity vulnerability in Gitea, published on 1 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-119627 in the wild and no public exploit code.

Affected product: Gitea. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119627/ (Markdown: https://insights.sbomify.com/CVE-2026-119627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119627
- OSV: https://osv.dev/vulnerability/CVE-2026-119627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119627/
Summaries are generated and may contain mistakes; the official description above is the record.