Forgejo up to 15.0.11/16.0.7/17.0.1 OpenID Login openid.go server-side request forgery

Summaryinfo

A vulnerability was found in Forgejo up to 15.0.11/16.0.7/17.0.1. It has been rated as problematic. The impacted element is an unknown function of the file modules/auth/openid/openid.go of the component OpenID Login. Performing a manipulation results in server-side request forgery. This vulnerability is identified as CVE-2026-119545. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Forgejo up to 15.0.11/16.0.7/17.0.1. This affects an unknown function of the file modules/auth/openid/openid.go of the component OpenID Login. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on 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 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.

It is possible to read the advisory at codeberg.org. This vulnerability is uniquely identified as CVE-2026-119545 since 10/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/30/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Forgejo

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.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion