Is CVE-2026-119545 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-119545 being exploited in the wild.

How severe is CVE-2026-119545?

Medium severity, with a CVSS score of 5.3, published 30 October 2026.

Which products and versions are affected?

Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1.

How is CVE-2026-119545 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-119545?

Check whether you run Forgejo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-119545: Forgejo server-side request forgery in OpenID discovery

CVE-2026-119545 · Severity: medium · CVSS 5.3 · Published 2026-10-30

Forgejo is a self-hosted Git forge platform that allows organizations to manage code repositories. When OpenID sign-in is enabled, unauthenticated attackers can trigger the server to make HTTP requests to arbitrary internal addresses, including loopback interfaces and cloud metadata endpoints. This enables port scanning, network reconnaissance, and potential data disclosure from internal services.

Technologies: Forgejo. Vendors: Forgejo.

Quick answers

Is CVE-2026-119545 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119545 being exploited in the wild.
How severe is CVE-2026-119545?: Medium severity, with a CVSS score of 5.3, published 30 October 2026.
Which products and versions are affected?: Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1.
Is there a fix for CVE-2026-119545?: No fixed version is recorded yet. Disable OpenID sign-in by setting ENABLE_OPENID_SIGNIN = false in the [openid] section of app.ini, or restrict the WHITELISTED_URIS to known safe OpenID providers only.</anigation> </invoke> If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-119545 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-119545?: Check whether you run Forgejo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Disable OpenID sign-in by setting ENABLE_OPENID_SIGNIN = false in the [openid] section of app.ini, or restrict the WHITELISTED_URIS to known safe OpenID providers only.</anigation> </invoke>

Technical details

The vulnerability is a server-side request forgery (SSRF) in the OpenID discovery handler at POST /user/login/openid. Unauthenticated attackers submit OpenID identifier URLs that are passed unsanitized to the yohcop openid-go library, which performs Yadis and HTML discovery requests using http.DefaultClient with no IP filtering or host validation. Unlike webhooks and migrations which apply network policies, the OpenID path bypasses these protections, allowing blind SSRF to loopback, RFC1918, and link-local addresses.

Affected products

Forgejo Forgejo through 15.0.11, 16.0.0 through 16.0.7, and 17.0.0 through 17.0.1

Timeline

2026-10-30: disclosed: CVE-2026-119545 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.