What is the CVSS score of EUVD-2026-41616?

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

Gitea EUVD-2026-41616

Q: Which versions of Gitea are affected by EUVD-2026-41616?

Gitea's repository-creation function lacks sufficient input validation in versions before 1.25.5, creating a pathway for authenticated users to submit malformed requests that could disrupt code…. A patch is available.

Q: How to fix or mitigate EUVD-2026-41616?

Within 24 hours: Identify all Gitea deployments and document current versions. Within 7 days: apply patches to upgrade all instances to Gitea 1.25.5 or later, prioritizing internet-facing deployments. Within 30 days: verify all Gitea instances are running patched versions and review any unusual repository creation activity logs from the pre-patch period.

| CVE-2026-22547 CRITICAL

Improper Input Validation (CWE-20)

2026-07-03 Gitea

GHSA-922f-hfwp-p56f

Information Disclosure Gitea Suse Gitea Open Source Git Server

9.1

CVSS 3.1 · Vendor: Gitea

View

Vulnerability Assessment

Weakness

CWE

CWE-20

OWASP Top 10:2025

A05:2025 - Injection

ASVS 5.0

V2 - Validation and Business Logic Input validation, allowlisting

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

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

Improper input validation in Gitea Open Source Git Server before 1.25.5 lets authenticated users submit repository-creation requests with unbounded template fields (issue labels, license, readme, fork branch) and unsupported trust-model or object-format values. The upstream fix (PRs 36671/36757) adds MaxSize length constraints and rejects any ObjectFormatName that is not sha1 or sha256. Rated CVSS 9.1 by the reporter, but no public exploit was identified, EPSS is only 0.17% (6th percentile), and CISA SSVC records exploitation status as none.

Affected VersionsENISA

Gitea Open Source Git Server 0 <1.25.5

Affected Packages

go code.gitea.io/gitea fix: 1.25.5

euvd gitea_open_source_git_server fix: 1.25.5

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 9.1 CRITICAL

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

SUSE CRITICAL

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

High

Availability

None

Lifecycle Timeline

CVE Published

Jul 03, 2026 - 20:19 cve.org

CRITICAL 9.1

CVE Published

Jul 03, 2026 - 20:19 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Gitea versions before 1.25.5 lack validation constraints for repository creation fields, including length-limited template fields and trust model or object format values.

Executive ViewAI

Why It Matters

Gitea's repository-creation function lacks sufficient input validation in versions before 1.25.5, creating a pathway for authenticated users to submit malformed requests that could disrupt code repository services. Organizations should prioritize patching to 1.25.5 to ensure repository integrity and development workflow continuity. While the technical severity is rated critical (CVSS 9.1), real-world exploitation risk is minimal (0.2% probability, no known active exploitation), making this a standard high-priority patch rather than an incident response.

Recommended Action

Within 24 hours: Identify all Gitea deployments and document current versions. Within 7 days: apply patches to upgrade all instances to Gitea 1.25.5 or later, prioritizing internet-facing deployments. Within 30 days: verify all Gitea instances are running patched versions and review any unusual repository creation activity logs from the pre-patch period.

Business Impact: Medium

Compensating Controls

Apply vendor patch: upgrade to Gitea 1.25.5 or later.

Threat Intelligence Overview

EPSS Score

0.2%

Top 94% 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 CRITICAL

CISA KEV No

Public POC No

EPSS 0.2%

Patch available Yes

Active threat No

Deciding rule

CRITICAL severity

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

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact

Medium

Technical Impact

Total

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +46

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.