dbcve.org
ArchiverApplication · Gfi

CVE-2026-2039

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
GFI Archiver MArc.Store Missing Authorization Authentication Bypass Vulnerability. This vulnerability allows remote attackers to bypass authentication on affected installations of GFI Archiver. Authentication is not required to exploit this vulnerability. The specific flaw exists within the configuration of the MArc.Store.Remoting.exe process, which listens on port 8018. The issue results from the lack of authorization prior to allowing access to functionality. An attacker can leverage this in conjunction with other vulnerabilities to execute code in the context of SYSTEM. Was ZDI-CAN-28597.

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

GFI Archiver contains a missing authorization vulnerability in the MArc.Store.Remoting.exe service that listens on port 8018. The remoting interface fails to perform authorization checks before executing functionality, allowing remote attackers to bypass authentication entirely and access sensitive features without credentials. This can be chained with other vulnerabilities to achieve SYSTEM-level code execution.

MitigationApply vendor patches immediately when available. As an immediate workaround, restrict network access to port 8018 using firewall rules or network segmentation to prevent unauthenticated external access to the vulnerable remoting service.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ArchiverApplication
Affected:= 15.10

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Verify GFI Archiver installation and version
    Check if GFI Archiver is installed and identify the exact version number. This can be done via Windows Programs and Features, registry keys (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\GFI Archiver), or by locating the installation directory.
    Affected if The installed version is exactly 15.10
  2. Confirm MArc.Store.Remoting.exe service is running
    Locate the MArc.Store.Remoting.exe process in Task Manager or via command line (tasklist /FI "IMAGENAME eq MArc.Store.Remoting.exe") and verify it is currently running.
    Affected if The service is running - the vulnerability exists in this specific service component.
  3. Check if port 8018 is listening
    Verify that the MArc.Store.Remoting.exe service is listening on port 8018 by running 'netstat -an | findstr 8018' or using a port scanner targeting localhost on that port.
    Affected if Port 8018 is open and listening - the vulnerable remoting interface is active.
  4. Assess network exposure of port 8018
    Determine if port 8018 is accessible from outside the local machine. This can be tested externally using a remote connection test or by checking firewall rules (netsh advfirewall firewall show rule name=all).
    Affected if Port 8018 is exposed to untrusted networks or the internet - enabling external unauthenticated attackers to reach the vulnerable service.

You are affected if GFI Archiver version 15.10 is installed, the MArc.Store.Remoting.exe service is running on port 8018, and that port is accessible to untrusted network actors.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches immediately when available. As an immediate workaround, restrict network access to port 8018 using firewall rules or network segmentation to prevent unauthenticated external access to the vulnerable remoting service.

Fix this in Archiver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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