# CVE-2026-88592: Server-side request forgery in n/a

> Attackers can bypass host whitelisting to fetch arbitrary internal URLs and read response data via the file proxy endpoint.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-xm5x-697f-2q56

## What is CVE-2026-88592?

CVE-2026-88592 is a critical server-side request forgery vulnerability in n/a, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

kkFileView >= 4.2.0 is vulnerable to Server-Side Request Forgery (SSRF). The cross-origin file proxy endpoint /getCorsFile is protected by TrustHostFilter against the trust.host whitelist. However, the URL parameter validated by the filter is not the same parameter the controller actually fetches: the filter validates the first non-empty parameter in a fixed priority order, while the controller only reads and fetches urlPath. By supplying both urlPath=<real target> and url=<whitelisted decoy address> in the same request, the decoy passes validation while the unvalidated real target is fetched server-side — and the response body is echoed back to the attacker.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2026-88592 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88592 is a critical server-side request forgery vulnerability in n/a, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-88592 exists.

Affected product: n/a. 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-88592/ (Markdown: https://insights.sbomify.com/CVE-2026-88592/index.md)
```

## Sources

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

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