Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-88592 – Server-Side Request Forgery (SSRF) – kkFileView ≥ 4.2.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-88592 is a critical Server-Side Request Forgery (SSRF) vulnerability affecting kkFileView, an open-source online document preview and file conversion platform. The flaw resides in the /getCorsFile endpoint, where a mismatch between the parameter validated by the access-control filter and the parameter actually fetched by the controller allows an unauthenticated attacker to force the server to make arbitrary outbound requests and retrieve the response content. The issue carries a CVSS v3.1 base score of 9.1 (Critical) and affects kkFileView 4.2.0 and later.

Technical details

  • Root cause: The TrustHostFilter validates the first non-empty parameter it encounters, in a fixed priority order (url → currentUrl → urlPath → urls), against a configured trusted-host whitelist. However, the OnlinePreviewController handling the /getCorsFile endpoint only reads and fetches the urlPath parameter, regardless of which parameter passed validation.
  • Trigger conditions: An attacker sends a single request to /getCorsFile supplying two parameters simultaneously: url set to a whitelisted/decoy address (which satisfies the filter’s check) and urlPath set to the actual target the attacker wants the server to fetch (e.g., an internal/intranet address). Because the filter only inspects url and stops there, the malicious urlPath value is never validated.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N/AC:L/PR:N/UI:N).
  • Impact: The server fetches attacker-specified URLs — including internal-only or loopback addresses — and echoes the response body back to the attacker, enabling reconnaissance and data exfiltration against internal services, cloud metadata endpoints, and other network-restricted resources reachable from the kkFileView host. The scoring reflects high confidentiality and integrity impact with no availability impact.

Affected software

  • kkFileView versions 4.2.0 and later (the vulnerable parameter-validation logic has been confirmed to persist through current master builds)

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: No official patched release has been published by the kkFileView project as of this writing. Security teams should monitor the project’s release channel for a fix that enforces consistent validation between the filter and the controller (i.e., validating the same parameter that is actually fetched).
  • Workarounds (until a patch is available):
    • Disable the affected endpoint entirely by setting kk.Getcorsfile = false in the kkFileView configuration if cross-origin file fetching is not required.
    • Deploy a WAF/reverse-proxy rule to strip or block the url and currentUrl parameters on requests to /getCorsFile, forcing all validation to occur against the actual fetched parameter.
    • Restrict network egress from the kkFileView host so it cannot reach internal-only services, loopback addresses, or cloud metadata endpoints, limiting the impact of any SSRF even if exploited.
    • Restrict inbound access to the kkFileView service to trusted networks only, reducing exposure to unauthenticated internet-based exploitation.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge