Nozomi Q-Free MaxTime up to 2.11.0 HTTP database.lua path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.8 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in Nozomi Q-Free MaxTime up to 2.11.0. This affects an unknown function of the file maxtime/api/database/database.lua of the component HTTP Handler. The manipulation leads to path traversal. This vulnerability is listed as CVE-2025-26357. The attack may be initiated remotely. There is no available exploit. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Nozomi Q-Free MaxTime up to 2.11.0. It has been rated as problematic. This issue affects an unknown code of the file maxtime/api/database/database.lua of the component HTTP Handler. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-35. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory. Impacted is confidentiality. The summary by CVE is:
A CWE-35 "Path Traversal" in maxtime/api/database/database.lua in Q-Free MaxTime less than or equal to version 2.11.0 allows an authenticated remote attacker to read sensitive files via crafted HTTP requests.
The weakness was presented by Diego Giubertoni. It is possible to read the advisory at nozominetworks.com. The identification of this vulnerability is CVE-2025-26357 since 02/07/2025. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.8VulDB Meta Temp Score: 3.8
VulDB Base Score: 2.7
VulDB Temp Score: 2.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.9
CNA Vector (Nozomi): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-35 / CWE-23 / CWE-22
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/07/2025 🔍02/12/2025 🔍
02/12/2025 🔍
10/28/2025 🔍
Sources
Advisory: nozominetworks.comResearcher: Diego Giubertoni
Status: Confirmed
CVE: CVE-2025-26357 (🔍)
GCVE (CVE): GCVE-0-2025-26357
GCVE (VulDB): GCVE-100-295523
Entry
Created: 02/12/2025 03:42 PMUpdated: 10/28/2025 07:02 PM
Changes: 02/12/2025 03:42 PM (63), 10/28/2025 07:02 PM (1)
Complete: 🔍
Cache ID: 244:43D:40
No comments yet. Languages: en.
Please log in to comment.