# CVE-2026-14985: CVE-2026-14985

> A local attacker can escalate privileges on Analog Way Picturall Quad Compact Mark II devices via a vulnerable maintenance script.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-49wx-869f-rxhj

## What is CVE-2026-14985?

CVE-2026-14985 is a high-severity vulnerability in Analog Way Picturall Quad Compact Mark II, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Analog Way Picturall Quad Compact Mark II version 3.5.8, contains a local privilege escalation vulnerability in the core firmware. This is due to improper privilege delegation and insufficient input validation in a maintenance script.

Weakness: CWE-250 (Execution with Unnecessary Privileges), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-14985 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14985 is a high-severity vulnerability in Analog Way Picturall Quad Compact Mark II, published on 22 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14985 in the wild and no public exploit code.

Affected product: Analog Way Picturall Quad Compact Mark II. 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-14985/ (Markdown: https://insights.sbomify.com/CVE-2026-14985/index.md)
```

## Sources

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

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