| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Gitea up to 1.22.1. It has been classified as problematic. This issue affects some unknown processing. The manipulation leads to confused deputy. This vulnerability is documented as CVE-2025-68944. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability was found in Gitea up to 1.22.1 and classified as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a confused deputy vulnerability. Using CWE to declare the problem leads to CWE-441. The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. Impacted is integrity. The summary by CVE is:
Gitea before 1.22.2 sometimes mishandles the propagation of token scope for access control within one of its own package registries.
The advisory is shared at blog.gitea.com. The identification of this vulnerability is CVE-2025-68944 since 12/26/2025. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 1.22.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-205415) and CERT Bund (WID-SEC-2025-2925). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Open Source Gitea
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.9VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔒
CNA Base Score: 5.0
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Confused deputyCWE: CWE-441
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Gitea 1.22.2
Patch: github.com
Timeline
12/26/2025 Advisory disclosed12/26/2025 CVE reserved
12/26/2025 VulDB entry created
01/03/2026 VulDB entry last update
Sources
Advisory: blog.gitea.comStatus: Confirmed
CVE: CVE-2025-68944 (🔒)
GCVE (CVE): GCVE-0-2025-68944
GCVE (VulDB): GCVE-100-338441
EUVD: 🔒
CERT Bund: WID-SEC-2025-2925 - Gitea: Mehrere Schwachstellen
Entry
Created: 12/26/2025 08:45Updated: 01/03/2026 11:09
Changes: 12/26/2025 08:45 (63), 12/26/2025 10:33 (1), 01/01/2026 05:26 (11), 01/03/2026 11:09 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.