# CVE-2018-1000803: Gitea Exposes Private Email Addresses

> Attackers can view private email addresses of other users by watching a repository and receiving notification emails.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f5fj-7265-jxhj, GO-2022-0823

## What is CVE-2018-1000803?

CVE-2018-1000803 is a medium-severity vulnerability in Gitea Gitea, published on 8 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gitea version prior to version 1.5.1 contains a CWE-200 vulnerability that can result in Exposure of users private email addresses. This attack appear to be exploitable via Watch a repository to receive email notifications. Emails received contain the other recipients even if they have the email set as private. This vulnerability appears to have been fixed in 1.5.1.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-1000803?

3 open source packages ship an affected version, including github.com/go-gitea/gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-gitea/gitea` | Go | All versions | 1.5.1 |
| `github.com/go-gitea/gitea` | Go | All versions | 1.5.1 |
| `github.com/go-gitea/gitea` | Go | All versions | 1.5.1 |

Products: Gitea Gitea.

## How do I fix CVE-2018-1000803?

Upgrade github.com/go-gitea/gitea to 1.5.1 or later.

## Is CVE-2018-1000803 being exploited?

There is no known exploitation of CVE-2018-1000803 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-2018-1000803 and fix it if it is affected.

What it is: CVE-2018-1000803 is a medium-severity vulnerability in Gitea Gitea, published on 8 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-1000803 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.5.1
- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.5.1
- github.com/go-gitea/gitea (Go): affected all versions; fixed in 1.5.1

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

## Sources

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

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