# CVE-2026-82556: Forgejo Repository Migration is_migrate_allowed.go net.LookupIP server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in Forgejo's repository migration handler to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-qcr2-8wjw-w786

## What is CVE-2026-82556?

CVE-2026-82556 is a medium-severity server-side request forgery vulnerability in Forgejo, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Forgejo up to 15.0.4. This issue affects the function net.LookupIP of the file services/migrations/allowlist/is_migrate_allowed.go of the component Repository Migration Handler. Performing a manipulation results in server-side request forgery. The attack can be initiated remotely. The exploit has been made public and could be used. The patch is named b313bb83f5ff22bcc0378e0e0ca7bbd58303f168. It is recommended to apply a patch to fix this issue. The project maintainer explains: "I don't intend to backport this to v15 or v16 as it is a breaking change."

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

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


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

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

## Is CVE-2026-82556 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82556 is a medium-severity server-side request forgery vulnerability in Forgejo, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82556 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-82556/ (Markdown: https://insights.sbomify.com/CVE-2026-82556/index.md)
```

## Sources

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

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