CVE-2026-119545

Forgejo through 15.0.11, 16.0.7, and 17.0.1 SSRF via OpenID Discovery

Published Oct 30, 2026 CVSS 4.0 · 6.9 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 a server-side request forgery vulnerability that allows unauthenticated attackers to make the server issue requests by submitting arbitrary OpenID identifier URLs. Attackers can POST crafted identifiers to /user/login/openid to trigger blind discovery GET requests to loopback, cloud metadata, and internal addresses for port scanning and probing.

Analysis

AI-generated

Technical impact

Forgejo versions 15.0.11, 16.0.7, and 17.0.1 contain a server‑side request forgery flaw that lets an unauthenticated attacker trigger the server to perform blind GET requests by posting crafted OpenID identifier URLs to the /user/login/openid endpoint. The attacker can make the server query loopback interfaces, cloud metadata services, and other internal addresses, effectively scanning and probing the network. This results in potential exposure of internal services and network topology without needing authentication or elevated privileges.

Affected Systems

The vulnerability affects Forgejo, the self‑hosted Git server, in the following releases: 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1. Users running any of these versions should confirm their exact patch level and plan an update accordingly.

Risk and Exploitability

The flaw carries a CVSS score of 6.9, indicating moderate severity. EPSS data is not available and the vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread exploit activity has been recorded yet. The attack vector requires only a simple POST request to /user/login/openid and no prior authentication, making exploitation straightforward for an attacker who can reach the Forgejo instance over the network.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Forgejo to a supported release that addresses the SSRF issue (for example, 15.0.12 or later, 16.0.8 or later, or 17.0.2 or later).
  • If upgrading is not immediately possible, restrict outbound traffic from the Forgejo server using firewall rules so that it cannot connect to internal or cloud‑metadata endpoints.
  • Configure the /user/login/openid handler to validate and whitelist OpenID identifier URLs, ensuring only approved domains are accepted.

Generated by OpenCVE AI on October 30, 2026 at 13:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', '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 a server-side request forgery vulnerability that allows unauthenticated attackers to make the server issue requests by submitting arbitrary OpenID identifier URLs. Attackers can POST crafted identifiers to /user/login/openid to trigger blind discovery GET requests to loopback, cloud metadata, and internal addresses for port scanning and probing.
Title Forgejo through 15.0.11, 16.0.7, and 17.0.1 SSRF via OpenID Discovery
First Time appeared Forgejo
Forgejo forgejo
Weaknesses CWE-918
CPEs cpe:2.3:a:forgejo:forgejo:*:*:*:*:*:*:*:*
Vendors & Products Forgejo
Forgejo forgejo
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

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