# CVE-2026-116056: KodCloud KodExplorer Remote Download web.function.php request_url_safe server-side request forgery


- **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:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-mm82-7x4g-wvpv

## What is CVE-2026-116056?

CVE-2026-116056 is a medium-severity vulnerability in KodCloud KodExplorer, published on 25 Oct 2026. 

### Official description

A flaw has been found in KodCloud KodExplorer up to 4.56. Affected is the function request_url_safe of the file app/function/web.function.php of the component Remote Download. This manipulation causes server-side request forgery. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-116056 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116056 is a medium-severity vulnerability in KodCloud KodExplorer, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116056 in the wild and no public exploit code.

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

## Sources

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

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