NVD / CVE Program· CNA Gitea

CVE-2026-27657: Gitea email settings allow changing another user's primary email address

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Gitea Gitea Open Source Git Server 1.25.5.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Gitea Gitea Open Source Git Server 1.25.5 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Gitea versions before 1.25.5 allow a user to change another user's primary email address.

HighCVSS 7.5 · v3.1—No exploit Fix available

Published: Jul 3, 2026
Updated: Oct 25, 2026
EPSS: 0.4% · 39th percentile
CWE: CWE-639

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Gitea). Independent of NVD's CPE analysis and usually ahead of it.

Gitea Gitea Open Source Git Server
- before 1.25.5affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Go	code.gitea.io/gitea	before 1.25.5	1.25.5
openSUSE:Leap 16.0	govulncheck-vulndb	before 0.0.20260902T191204-160000.1.1	0.0.20260902T191204-160000.1.1
SUSE:Linux Enterprise Server 16.0	govulncheck-vulndb	before 0.0.20260902T191204-160000.1.1	0.0.20260902T191204-160000.1.1

Same product

gitea: all records

Other highest-scoring records for the same primary product.

CVE-2024-6886Inproper Sanitation of field leading to stored XSS
50Plan
CVE-2026-20896Gitea Docker image trusts spoofable reverse-proxy headers by default
40Plan
CVE-2026-56654Privilege Escalation via Access Token Scope Escalation in API
39Monitor

Published before and after this one in the same product

← EarlierCVE-2026-26292Jul 3, 2026 · Gitea LFS mirror synchronization bypasses migration HTTP transport restrictions
39Monitor
← EarlierCVE-2026-26307Jul 3, 2026 · Gitea git grep search lacks a timeout
30Monitor
Later →CVE-2026-27660Jul 3, 2026 · Gitea draft releases use insufficient permission checks
30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Gitea Gitea Open Source Git Server	1.25.5	Vendor (CNA)
Go:code.gitea.io/gitea	1.25.5	Package registry (OSV)
opensuse:govulncheck-vulndb	0.0.20260902T191204-160000.1.1 · openSUSE:Leap 16.0	Package registry (OSV)
suse:govulncheck-vulndb	0.0.20260902T191204-160000.1.1 · SUSE:Linux Enterprise Server 16.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

CsEnoxreporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-287400 days apartGitea LFS object reuse bypasses Code-unit authorization
28Monitor
CVE-2026-5788641 days apartCross-repository issue/comment attachment re-linking can expose private attachment content
23Monitor
CVE-2026-257820 days apartGitea tracked-time deletion can target entries from another issue
21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0506 · Jul 8, 2026(Gitea Güvenlik Zafiyeti)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const invoice = await Invoice.findById(req.params.id);
2res.json(invoice);

Fixed

1const invoice = await Invoice.findOne({
2  id: req.params.id,
3  ownerId: req.user.id,
4});
5if (!invoice) return res.sendStatus(404);
6res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

blog.gitea.com/release-of-1.25.5/

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records