dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-42881

HIGH · 8.4 CVSS v4.0 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

STIGQter fails to properly sanitize or validate data from .stigqter files during the HTML export process. When a user opens a malicious .stigqter file and executes the Export HTML function, the application processes unsanitized input, allowing arbitrary code execution in the context of the user running the application.

MitigationUpgrade to STIGQter version 1.2.7 or later. Until then, avoid opening untrusted .stigqter files and refrain from using the Export HTML function on files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if STIGQter is installed
    Search for STIGQter in installed programs (Windows: Add/Remove Programs, Programs and Features; Linux/Mac: check common application directories or package managers)
    Affected if STIGQter is found installed on the system
  2. Determine installed STIGQter version
    Locate the installed STIGQter application and check its version information (typically available in About dialog, executable properties, or version file within the application directory)
    Affected if The version number is 0.1.2 through 1.2.6 (inclusive) - meaning any version from 0.1.2 up to but not including 1.2.7
  3. Verify .stigqter file association or import capability
    Check if the application can import or open .stigqter files - look for file import functionality or file type associations in the application
    Affected if The application processes .stigqter files as part of normal operation
  4. Confirm Export HTML feature presence
    Locate the Export HTML action/feature within the STIGQter application interface (typically found in file, export, or actions menus)
    Affected if The Export HTML functionality is available and accessible to users

A user is affected if STIGQter version 0.1.2 through 1.2.6 is installed AND the application processes .stigqter files with the Export HTML feature enabled, particularly if users open files from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to STIGQter version 1.2.7 or later. Until then, avoid opening untrusted .stigqter files and refrain from using the Export HTML function on files from untrusted sources.

Recommended fix High confidence

1.2.7 or later

  1. 1. Backup any existing STIGQter data, configurations, and custom .stigqter files
  2. 2. Uninstall or remove the current version of STIGQter
  3. 3. Obtain STIGQter version 1.2.7 or later from the official project repository (github.com)
  4. 4. Install version 1.2.7 following standard installation procedures
  5. 5. Verify the installed version is 1.2.7 or later
  6. 6. Do not open untrusted .stigqter files from unknown sources

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42881 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data