Path Traversal in STIGQter (CVE-2026-42881)
Summary
Path traversal in STIGQter (CVE-2026-42881). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.2.7 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42881 has been found in STIGQter.
Risk of unauthorized operations or information disclosure.
What to do: upgrade STIGQter to 1.2.7 or later.
If unsure, ask your IT team or search "STIGQter CVE-2026-42881" on the vendor's site.
CVE-2026-42881 (STIGQter) — CWE-22
Patched: 1.2.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in STIGQter.
Check the vendor advisory for the affected versions of STIGQter.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.2.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'STIGQter' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'STIGQter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
STIGQterを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade STIGQter to 1.2.7ステージング環境で 1.2.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory bitwizemusic.com
- advisory github.com
- advisory nvd.nist.gov
- report bitwizemusic.com