# CVE-2026-103667: Gitea container registry stored XSS through blob media type

> Authenticated users can execute arbitrary JavaScript on the Gitea origin via malicious container blobs, potentially leading to account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** BIT-gitea-2026-103667, GHSA-7cq7-4v93-8wjm, MINI-238q-56wg-x5jq, MINI-959g-mhh7-6945

## What is CVE-2026-103667?

CVE-2026-103667 is a medium-severity cross-site scripting vulnerability in Gitea Gitea, published on 6 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in pushed image manifests, without a `Content-Disposition` or restrictive content security policy. A user who can push container images can publish a blob containing HTML and JavaScript with a `text/html` media type. When a victim who is authenticated to the instance opens the blob URL in a browser, the script runs on the Gitea origin and can perform actions as the victim, such as creating API tokens.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

1 open source package ship an affected version, including gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitea` | Bitnami | All versions | 28.0.0 |

Products: Gitea Gitea.

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

Upgrade gitea to 28.0.0 or later.

## Is CVE-2026-103667 being exploited?

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

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-103667 is a medium-severity cross-site scripting vulnerability in Gitea Gitea, published on 6 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-103667 in the wild and no public exploit code.

Affected packages and fixed versions:
- gitea (Bitnami): affected all versions; fixed in 28.0.0

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-103667/ (Markdown: https://insights.sbomify.com/CVE-2026-103667/index.md)
```

## Sources

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

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