# CVE-2026-85082: Maple Media Root Browser Classic 3.3.0 - OS command injection through crafted SQLite filenames

> Attackers can execute arbitrary OS commands by crafting malicious SQLite filenames in Root Browser Classic, potentially compromising the device.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-rqjf-4x9c-c8v8

## What is CVE-2026-85082?

CVE-2026-85082 is a high-severity command injection vulnerability in Maple Media Root Browser Classic, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Root Browser Classic 3.3.0 passes the path of a selected SQLite database to an operating-system shell without safely separating the filename from the command.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-85082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85082 is a high-severity command injection vulnerability in Maple Media Root Browser Classic, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85082 exists.

Affected product: Maple Media Root Browser Classic. 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-85082/ (Markdown: https://insights.sbomify.com/CVE-2026-85082/index.md)
```

## Sources

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

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