# CVE-2026-116110: GiantappMan LiveWallPaper SignalR Hub UploadFile missing authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-q96p-8xmw-x2vw

## What is CVE-2026-116110?

CVE-2026-116110 is a medium-severity vulnerability in GiantappMan LiveWallPaper, published on 26 Oct 2026. 

### Official description

A vulnerability was found in GiantappMan LiveWallPaper 2.6.8.0 on Windows. This issue affects some unknown processing of the file /LiveWallpaper/UploadFile of the component SignalR Hub. Performing a manipulation results in missing authentication. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The patch is named b62f878899adbfc2968e3345442f3a3df91b774d. It is suggested to install a patch to address this issue. The vendor was contacted early about this disclosure.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-116110 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116110 is a medium-severity vulnerability in GiantappMan LiveWallPaper, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116110 in the wild and no public exploit code.

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

## Sources

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

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