CVE-2025-26354
Q-Free Maxtime ≤ 2.11.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-26354 is a high-severity Path Traversal: '.../...//' (CWE-35) vulnerability in Q-Free Maxtime. Its CVSS base score is 7.2 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 46% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Q-Free MaxTime versions 2.11.0 and earlier contain a path traversal vulnerability (CWE-35) in the copy endpoint of maxtime/api/database/database.lua. The flaw allows an authenticated remote attacker to supply crafted HTTP requests that overwrite arbitrary files on the underlying system. It is tracked as CVE-2025-26354 and carries a CVSS 3.1 base score of 7.2.
An attacker who already possesses valid credentials can leverage the endpoint to modify sensitive configuration or data files, resulting in high impact to confidentiality, integrity, and availability without any user interaction required.
The referenced Nozomi Networks advisory at https://www.nozominetworks.com/labs/vulnerability-advisories-cve-2025-26354 supplies additional technical context and recommended actions for affected deployments. The associated EPSS values have remained low, with a current score of 0.0214 and a recorded peak of 0.0269.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-4166
Vulnerability Data
A CWE-35 "Path Traversal" in maxtime/api/database/database.lua (copy endpoint) in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated remote attacker to overwrite sensitive files via crafted HTTP requests.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly neutralizes path sequences so the traversal cannot be introduced or exploited.
Enforces access authorizations on the resulting pathname, blocking traversal attempts from succeeding.
Enforces information flow rules that stop unauthorized directory escapes via crafted paths.
Least privilege reduces the impact of any successful traversal by limiting accessible resources.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and path sanitization that neutralize traversal sequences.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect path-traversal flaws before release.
Secure SDLC mandates input validation and path-handling controls that directly mitigate path traversal.
Application security requirements include rules for safe file-path construction and canonicalization.
Secure architecture principles require proper directory restrictions and input sanitization to prevent traversal.
Secure coding standards explicitly forbid unsafe path concatenation and mandate canonicalization routines.
Information access restriction limits file reachability but does not address the input-validation flaw itself.