# CVE-2026-42881: STIGQter: Arbitrary File Write leading to Local Code Execution via Export HTML

> An attacker can achieve local code execution by tricking a user into exporting a malicious STIG file to HTML, allowing arbitrary file writes.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/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:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-mcv5-5j7p-vqh7

## What is CVE-2026-42881?

CVE-2026-42881 is a high-severity path traversal vulnerability in squinky86 STIGQter, published on 14 May 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

STIGQter is an open-source reimplementation of DISA's STIG Viewer. From 0.1.2 to before 1.2.7, an attacker can achieve local code execution (LCE) with the privileges of the user running STIGQter. This requires user interaction: the victim must open the malicious .stigqter file and explicitly run the "Export HTML" action. This vulnerability is fixed in 1.2.7.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-42881 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42881 is a high-severity path traversal vulnerability in squinky86 STIGQter, published on 14 May 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-42881 exists.

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

## Sources

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

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