CVE-2026-119547

Forgejo through 15.0.11, 16.0.7, and 17.0.1 Information Disclosure via /api/v1/user/keys/{id}

Published Oct 30, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Forgejo's GetPublicKey API endpoint lacks an ownership check, allowing authenticated users with a read:user token or session to retrieve the titles, fingerprints, and public key material of any user's SSH, deploy, and principal keys. This information disclosure can aid attackers in social engineering or further compromise by revealing key characteristics that may help in targeted attacks. The vulnerability is characterized as a lack of ownership verification (CWE‑639).

Affected Systems

Forgejo servers running versions 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1 are impacted. The issue is present in the product "Forgejo" from Abraxas Labs and affects the API route /api/v1/user/keys/{id}. No other vendors or product variants are listed in the CNA data.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, but no EPSS score is available, so the likelihood of exploitation cannot be precisely measured. The vulnerability is not currently listed in CISA's KEV catalog. The likely attack vector involves an authenticated user making successive requests to /api/v1/user/keys/{id} with sequential identifiers to enumerate other users' keys; the endpoint returns useful metadata without requiring additional privileges.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Forgejo to a patched version (≥17.0.2) that enforces ownership checks on the GetPublicKey API.
  • If an upgrade is not possible immediately, restrict the /api/v1/user/keys/{id} endpoint to higher‑privilege tokens or disable it for normal users.
  • Monitor API logs for repeated sequential key ID requests to detect possible enumeration attempts.

Generated by OpenCVE AI on October 30, 2026 at 12:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Forgejo through 15.0.11, 16.0.7, and 17.0.1 Information Disclosure via /api/v1/user/keys/{id}
First Time appeared Forgejo
Forgejo forgejo
Weaknesses CWE-639
CPEs cpe:2.3:a:forgejo:forgejo:*:*:*:*:*:*:*:*
Vendors & Products Forgejo
Forgejo forgejo
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 5, 2026, 9:20 PM
Reserved
Oct 30, 2026, 10:53 AM
Status
Deferred
Published
Oct 30, 2026, 12:16 PM
Modified
Nov 5, 2026, 10:17 PM