# CVE-2026-119545: Forgejo through 15.0.11, 16.0.7, and 17.0.1 SSRF via OpenID Discovery


- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-877c-6q9f-v4cw

## What is CVE-2026-119545?

CVE-2026-119545 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-119545?


## How do I fix CVE-2026-119545?

No fix has been published for CVE-2026-119545 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119545 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119545 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119545 and fix it if it is affected.

What it is: CVE-2026-119545 is a medium-severity vulnerability in forgejo, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119545 exists.

Affected product: forgejo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119545/ (Markdown: https://insights.sbomify.com/CVE-2026-119545/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119545
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119545
- OSV: https://osv.dev/vulnerability/CVE-2026-119545

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119545/
Summaries are generated and may contain mistakes; the official description above is the record.