# CVE-2026-104627: Gitea OpenID account linking without session binding

> Attackers can hijack user accounts by linking their OpenID identity to a victim's session, bypassing local authentication checks like TOTP.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-mf69-7pqq-86vx

## What is CVE-2026-104627?

CVE-2026-104627 is a medium-severity authentication bypass vulnerability in Gitea, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The Gitea OpenID association callback in the security settings accepted a positive OpenID 2.0 assertion without checking that the signed-in user had started the linking. Because OpenID 2.0 allows unsolicited assertions, an attacker-controlled OpenID provider could attach the attacker's identity to the account of a signed-in victim who opened a crafted link, and the attacker could then sign in as the victim through OpenID login, which does not apply the local TOTP or WebAuthn checks. The callback now requires a time-limited `state` value bound to the user.

Weakness: CWE-352 (Cross-Site Request Forgery), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-104627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-104627 is a medium-severity authentication bypass vulnerability in Gitea, published on 18 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-104627 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-104627/ (Markdown: https://insights.sbomify.com/CVE-2026-104627/index.md)
```

## Sources

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

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