dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-1186

HIGH · 8.6 CVSS v4.0 Published 2026-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable 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
EAP Legislator is vulnerable to Path Traversal in file extraction functionality. Attacker can prepare zipx archive (default file type used by the Legislator application) and choose arbitrary path outside the intended directory (e.x. system startup) where files will be extracted by the victim upon opening the file. This issue was fixed in version 2.25a.

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

EAP Legislator contains a path traversal vulnerability in its zipx archive extraction functionality. Attackers can craft malicious zipx archives containing file paths with directory traversal sequences (e.g., ../../../) that cause files to be extracted outside the intended directory when victims open the archive, potentially placing executable files in startup locations.

MitigationUpgrade to version 2.25a or later. Until upgraded, avoid opening zipx attachments 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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L/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. Confirm EAP Legislator installation
    Locate EAP Legislator on the system via installed programs list or program directory
    Affected if EAP Legislator software is found on the system
  2. Identify installed version
    Access the About or Help section within EAP Legislator, or right-click the main executable and select Properties to view version information
    Affected if A version number is displayed that is lower than 2.25a
  3. Verify zipx extraction functionality
    Confirm that the zipx archive extraction feature is present and enabled in the installed version (this is a core function of the software)
    Affected if The zipx extraction capability exists in the installation
  4. Check for recent zipx file processing
    Review recent activity logs, recent files, or user history for zipx archives opened or extracted using EAP Legislator
    Affected if Zipx files from untrusted sources have been opened or extracted recently

A user is affected if EAP Legislator version 2.24 or earlier is installed and the zipx extraction feature has been used to open archives, particularly 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 version 2.25a or later. Until upgraded, avoid opening zipx attachments from untrusted sources.

Recommended fix Moderate confidence

EAP Legislator version 2.25a

  1. 1. Check the current installed version of EAP Legislator by opening the application and navigating to Help > About or checking the software documentation
  2. 2. Download EAP Legislator version 2.25a or later from the official vendor source
  3. 3. Before upgrading, backup any important data and configuration files associated with the application
  4. 4. Uninstall the current version of EAP Legislator or run the installer to upgrade in place
  5. 5. Install version 2.25a or newer following the vendor's installation instructions
  6. 6. After installation, verify the version number matches 2.25a or higher
  7. 7. Test that the file extraction functionality works correctly with zipx archives to confirm the path traversal vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1186 — 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-1186 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