# CVE-2026-19909: PAX Technology Q80 AIP File Parsing Link Following Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code as root via symbolic link abuse in AIP file parsing.

- **Severity:** High 7.5 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-83w9-7r9f-f3qm

## What is CVE-2026-19909?

CVE-2026-19909 is a high-severity path traversal vulnerability in PAX Technology Q80, published on 14 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PAX Technology Q80 AIP File Parsing Link Following Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of PAX Technology Q80. Authentication is not required to exploit this vulnerability.

The specific flaw exists within the parsing of AIP files. By creating a symbolic link, an attacker can abuse the installer process to write arbitrary files. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of root. Was ZDI-CAN-30583.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2026-19909 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19909 is a high-severity path traversal vulnerability in PAX Technology Q80, published on 14 Aug 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-19909 in the wild and no public exploit code.

Affected product: PAX Technology Q80. 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-19909/ (Markdown: https://insights.sbomify.com/CVE-2026-19909/index.md)
```

## Sources

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

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