What is the CVSS score of CVE-2026-24451?

CVE-2026-24451 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.2%.

Gitea CVE-2026-24451

EUVD-2026-41619 HIGH

Information Exposure (CWE-200)

2026-07-03 Gitea

GHSA-wrf9-r3h7-7x5v

Information Disclosure Gitea Suse Gitea Open Source Git Server

7.5

CVSS 3.1 · Vendor: Gitea

View

Vulnerability Assessment

Weakness

CWE

CWE-200

OWASP Top 10:2025

A01:2025 - Broken Access Control

ASVS 5.0

V14 - Data Protection Data exposure prevention

MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 22, 2026

Information disclosure in Gitea 1.26.2 lets a fork owner keep pulling commits from a parent repository via the merge-upstream API even after the parent was switched from public to private, exposing content the fork should no longer be authorized to see. The flaw stems from the synchronization endpoint failing to re-check the parent's current visibility, so data added during the private period leaks into a fork whose owner can no longer directly access the parent. A working proof-of-concept is publicly published and CISA SSVC rates exploitation automatable, but the issue is not on CISA KEV and EPSS is low (0.20%); it is fixed in Gitea 1.26.3.

Affected VersionsENISA

Gitea Open Source Git Server 1.26.2

Affected Packages

go code.gitea.io/gitea fix: 1.26.3

euvd gitea_open_source_git_server no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in go, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Know when Gitea gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (Gitea) PRIMARY 7.5 HIGH

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

SUSE HIGH

Primary rating from Vendor (Gitea).

CVSS VectorVendor: Gitea

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVE Published

Jul 03, 2026 - 20:19 cve.org

UNKNOWN (no severity yet)

CVE Published

Jul 03, 2026 - 20:19 cve.org

HIGH 7.5

DescriptionCVE.org

Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

Executive ViewAI

Why It Matters

Gitea 1.26.2 contains an information disclosure vulnerability in its repository merge-upstream API that allows fork owners to access confidential content from parent repositories after they transition from public to private; publicly available exploit code exists. This exposes sensitive code and data to former collaborators, presenting a material compliance and intellectual property risk for organizations managing proprietary repositories.

Recommended Action

Within 24 hours, identify all Gitea instances running versions 1.26.0-1.26.2. Within 7 days, upgrade affected instances to Gitea 1.26.3 or later and verify the merge-upstream endpoint functions correctly post-upgrade. Within 30 days, conduct a repository access-control audit, review any repositories transitioned from public to private during the vulnerable period, and test fork synchronization behavior to confirm unauthorized access is blocked.

Business Impact: High

Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score

0.2%

Top 90% exploitable

Threat Intel

1 sources

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment GHSA Vendor

GitHub

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Out-of-Cycle

Exploitation

Poc

System Exposure· derived

Open

Automatable

Yes

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.