# CVE-2026-112350: Sunhillo SureLine Path Traversal via radarUpdater.cgi


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-q7gg-whqr-w8f9

## What is CVE-2026-112350?

CVE-2026-112350 is a high-severity vulnerability in Sunhillo Corporation SureLine, published on 27 Oct 2026. 

### Official description

Sunhillo SureLine before 9.1.5 contains a path traversal vulnerability in the radarUpdater.cgi endpoint that allows unauthenticated remote attackers to read arbitrary files with root privileges due to missing authentication checks and insufficient sanitization of the filename parameter. Attackers can use directory traversal sequences to access sensitive files such as /etc/shadow, the web user database, the root SSH private key, and the device's TLS private key, leading to full system compromise.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-112350 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112350 is a high-severity vulnerability in Sunhillo Corporation SureLine, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112350 in the wild and no public exploit code.

Affected product: Sunhillo Corporation SureLine. 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-112350/ (Markdown: https://insights.sbomify.com/CVE-2026-112350/index.md)
```

## Sources

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

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