# CVE-2026-85614: OpenPanel API before 2.3.0 Unauthenticated SSRF via site-checker

> Unauthenticated attackers can exploit the site-checker endpoint to perform Server-Side Request Forgery, accessing internal services and cloud metadata.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-gqcr-xgfj-pq29, GHSA-jx42-589g-c2x6

## What is CVE-2026-85614?

CVE-2026-85614 is a critical server-side request forgery vulnerability in Openpanel-dev openpanel, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenPanel before 2.3.0 contains an unauthenticated server-side request forgery vulnerability in the GET /tools/site-checker endpoint that accepts a fully client-controlled URL parameter with no private IP filtering or DNS-rebinding protection. Attackers can make the OpenPanel server issue requests to internal services, localhost, and cloud metadata endpoints, reading internal HTTP response titles, headers, status codes, and SSL certificate information.

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

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


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

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

## Is CVE-2026-85614 being exploited?

There is no known exploitation of CVE-2026-85614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85614 is a critical server-side request forgery vulnerability in Openpanel-dev openpanel, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85614 in the wild and no public exploit code.

Affected product: Openpanel-dev openpanel. 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-85614/ (Markdown: https://insights.sbomify.com/CVE-2026-85614/index.md)
```

## Sources

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

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