dbcve.org
ArchiverApplication · Gfi

CVE-2026-2037

HIGH · 8.8 CVSS v3.0 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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.Core Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GFI Archiver. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the configuration of the MArc.Core.Remoting.exe process, which listens on port 8017. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-27935.

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

This is a deserialization RCE vulnerability in GFI Archiver's MArc.Core.Remoting.exe service listening on port 8017. The flaw stems from lack of proper validation of user-supplied data during deserialization, allowing remote attackers to execute arbitrary code as SYSTEM. Although authentication is required, it can be bypassed.

MitigationApply vendor-provided patch for CVE-2026-2037 when available; until then, restrict network access to port 8017 to trusted IPs only and monitor for signs of exploitation.

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Identify GFI Archiver installation and version
    Check for GFI Archiver installation directory (typically C:\Program Files\GFI\Archiver or similar) and locate a version file or check the product about dialog. Alternatively, query the Windows registry under HKLM\SOFTWARE\GFI\Archiver for the InstallVersion value.
    Affected if Installed version is exactly 15.10
  2. Verify MArc.Core.Remoting.exe service is running
    Open Windows Services (services.msc) or run 'sc query MArc.Core.Remoting' or 'tasklist /FI "IMAGENAME eq MArc.Core.Remoting.exe"' to check if the service process is active.
    Affected if The MArc.Core.Remoting.exe process is running on the system
  3. Confirm port 8017 is listening
    Run 'netstat -ano | findstr :8017' or use PowerShell 'Test-NetConnection -ComputerName localhost -Port 8017' to verify the remoting service is accepting connections.
    Affected if Port 8017 is in LISTENING state and bound to a listening process
  4. Check network exposure of port 8017
    Review firewall rules (Windows Firewall or external firewall) to determine if port 8017 is open to untrusted network segments. Run 'netsh advfirewall firewall show rule name=all' or inspect external firewall policies.
    Affected if Port 8017 is accessible from network segments outside trusted administration IPs

A system is affected if GFI Archiver version 15.10 is installed, the MArc.Core.Remoting.exe service is running, and port 8017 is exposed to untrusted networks.

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-provided patch for CVE-2026-2037 when available; until then, restrict network access to port 8017 to trusted IPs only and monitor for signs of exploitation.

Fix this in Archiver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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