Forgejo up to 15.0.11/16.0.7/17.0.1 GetPublicKey API key.go information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 2.28- |
Summary
A vulnerability, which was classified as problematic, has been found in Forgejo up to 15.0.11/16.0.7/17.0.1. The affected element is an unknown function of the file key.go of the component GetPublicKey API Handler. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2026-119547. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Forgejo up to 15.0.11/16.0.7/17.0.1 and classified as problematic. This issue affects an unknown functionality of the file key.go of the component GetPublicKey API Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1 contains an information disclosure vulnerability in the GetPublicKey API handler that lacks an ownership check on key lookups. Authenticated users with a read:user token or session can enumerate sequential key IDs to obtain titles, fingerprints and public key material of other users' SSH, deploy and principal keys.
The advisory is shared at codeberg.org. The identification of this vulnerability is CVE-2026-119547 since 10/30/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 15.0.0
- 15.0.1
- 15.0.2
- 15.0.3
- 15.0.4
- 15.0.5
- 15.0.6
- 15.0.7
- 15.0.8
- 15.0.9
- 15.0.10
- 15.0.11
- 16.0.0
- 16.0.1
- 16.0.2
- 16.0.3
- 16.0.4
- 16.0.5
- 16.0.6
- 16.0.7
- 17.0.0
- 17.0.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (VulnCheck): 🔒
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/30/2026 Advisory disclosed10/30/2026 CVE reserved
10/30/2026 VulDB entry created
10/30/2026 VulDB entry last update
Sources
Advisory: codeberg.orgStatus: Not defined
CNA: VulnCheck
CVE: CVE-2026-119547 (🔒)
GCVE (CVE): GCVE-0-2026-119547
GCVE (VulDB): GCVE-100-429017
Entry
Created: 10/30/2026 12:50Changes: 10/30/2026 12:50 (73)
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.