# CVE-2026-34009: **Container Escape** Host user home directory mounted with write access into application container

> A local administrator can escape the application container to compromise the host system due to improper isolation of the home directory.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-qj84-cjxx-3366

## What is CVE-2026-34009?

CVE-2026-34009 is a high-severity vulnerability in QNAP Systems Inc. Notes Station 3, published on 15 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An improper isolation or compartmentalization vulnerability has been reported to affect Notes Station 3. If a local attacker gains an administrator account, they can then exploit the vulnerability to compromise the security of the system.

We have already fixed the vulnerability in the following version:
Notes Station 3 3.9.11 and later

Weakness: CWE-653 (Improper Isolation or Compartmentalization)

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


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

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

## Is CVE-2026-34009 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34009 is a high-severity vulnerability in QNAP Systems Inc. Notes Station 3, published on 15 Oct 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-34009 in the wild and no public exploit code.

Affected product: QNAP Systems Inc. Notes Station 3. 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-34009/ (Markdown: https://insights.sbomify.com/CVE-2026-34009/index.md)
```

## Sources

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

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