dbcve.org
M Files ServerApplication · M Files

CVE-2026-0932

HIGH · 7.3 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 26.3.15818.5 or later.
See remediation →
82/100
Remediation priority · High
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
Blind server-side request forgery (SSRF) vulnerability in legacy connection methods of document co-authoring features in M-Files Server before 26.3 allow an unauthenticated attacker to cause the server to send HTTP GET requests to arbitrary URLs.

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

A blind server-side request forgery (SSRF) vulnerability exists in legacy connection methods of the document co-authoring feature in M-Files Server versions prior to 26.3. An unauthenticated remote attacker can cause the affected server to send HTTP GET requests to attacker-controlled arbitrary URLs, potentially enabling internal network reconnaissance or interaction with internal services.

MitigationUpgrade M-Files Server to version 26.3 or later to obtain the security patch. If immediate upgrade is not feasible, consider disabling or restricting legacy connection methods for document co-authoring and implement network segmentation to limit outbound connections from the server.

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
M Files ServerApplication
Affected:< 26.3.15818.5

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
Low
Integrity
Low
Availability
Low

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

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. Check M-Files Server version
    Open M-Files Admin, navigate to the server node, or run 'mfserveradmin /showversion' from command line to retrieve the installed version number
    Affected if Version is lower than 26.3.15818.5 (for example, 26.2.x, 26.1.x, or earlier)
  2. Verify document co-authoring is enabled
    In M-Files Admin, expand the vault properties and look for 'Document Co-Authoring' or 'Concurrent Editing' settings under vault configuration
    Affected if The document co-authoring feature is enabled for any vault
  3. Identify legacy connection method configuration
    In M-Files Admin under vault settings, locate the connection methods for document co-authoring. Look for options labeled 'legacy', 'direct', or 'classic' connection modes
    Affected if Legacy connection methods are available or enabled for the vault
  4. Review outbound network activity
    Monitor network traffic from the M-Files Server using tools like Wireshark, NetFlow analysis, or Windows Firewall audit logs for unexpected outbound HTTP GET requests
    Affected if Server is making outbound HTTP requests to unfamiliar or internal IP addresses without user-initiated document access
  5. Check for unauthenticated access paths
    Review network exposure of M-Files Server - verify whether the server is directly accessible from untrusted networks without VPN or firewall restrictions
    Affected if The M-Files Web or REST API endpoints are exposed to untrusted networks without authentication barriers

You are affected if your M-Files Server version is below 26.3.15818.5 AND the document co-authoring feature with legacy connection methods is enabled and accessible to unauthenticated users.

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
Upgrade available Upgrade to 26.3.15818.5 or later
Fixed in 26.3.15818.5
Interim mitigation

Upgrade M-Files Server to version 26.3 or later to obtain the security patch. If immediate upgrade is not feasible, consider disabling or restricting legacy connection methods for document co-authoring and implement network segmentation to limit outbound connections from the server.

Recommended fix High confidence

M-Files Server version 26.3.15818.5 or later

  1. 1. Identify the current version of M-Files Server installed by checking the M-Files Server administrator interface or using the M-Files administration tools
  2. 2. Navigate to the official M-Files download portal at product.m-files.com or empower.m-files.com
  3. 3. Download M-Files Server version 26.3.15818.5 or any subsequent version that supersedes it
  4. 4. Create a complete backup of the M-Files Server configuration and database before proceeding with the upgrade
  5. 5. Stop the M-Files Server service to ensure a safe upgrade process
  6. 6. Install the downloaded M-Files Server version 26.3.15818.5 or later following the standard M-Files upgrade procedure
  7. 7. Restart the M-Files Server service after the upgrade completes
  8. 8. Verify that the server is operational and the legacy connection methods have been updated or removed

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

Fix this in M Files Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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