Unauthenticated memory disclosure via incorrect buffer check
Published Aug 25, 2023 · Updated Feb 23, 2026
An out-of-bounds read in M-Files Server before 23.8.12892.6 or 23.2 LTS SR3 allows remote attackers to read limited process memory. An incorrect memory-buffer size check permits a request to read beyond the intended boundary; M-Files has not disclosed the affected parser, field, or endpoint. No authentication or user interaction is required, and the vendor bounds the disclosed confidentiality consequence to a small memory read.
Summary
What happened
An out-of-bounds read in M-Files Server before 23.8.12892.6 or 23.2 LTS SR3 allows remote attackers to read limited process memory. An incorrect memory-buffer size check permits a request to read beyond the intended boundary; M-Files has not disclosed the affected parser, field, or endpoint. No authentication or user interaction is required, and the vendor bounds the disclosed confidentiality consequence to a small memory read.
The record
- CVE
- CVE-2023-3425
- Published
- Aug 25, 2023
- Updated
- Feb 23, 2026
- Vendor
- M-Files
- Product
- M-Files Server
- Classifications
- CWE-125, CAPEC-540, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2023CVE publishedPublication date reported by the CVE source.
- Feb 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <23.8.12892.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo