dromara lamp-cloud up to 5.10.0 chunk-check endpoint FileChunkController.java Name path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 1.04+ |
Summary
A vulnerability marked as critical has been reported in dromara lamp-cloud up to 5.10.0. Impacted is an unknown function of the file FileChunkController.java of the component chunk-check endpoint. The manipulation of the argument Name leads to path traversal. This vulnerability is listed as CVE-2026-19758. The attack may be initiated remotely. In addition, an exploit is available. The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as critical, has been found in dromara lamp-cloud up to 5.10.0. This issue affects an unknown code of the file FileChunkController.java of the component chunk-check endpoint. The manipulation of the argument name with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality, integrity, and availability.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-19758. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
The exploit is available at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
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-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
08/13/2026 Advisory disclosed08/13/2026 VulDB entry created
08/13/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 413
Status: Not defined
CVE: CVE-2026-19758 (🔒)
GCVE (CVE): GCVE-0-2026-19758
GCVE (VulDB): GCVE-100-389603
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/13/2026 17:45Changes: 08/13/2026 17:45 (60)
Complete: 🔍
Submitter: Ku4D3
Cache ID: 216::103
Submit
Accepted
- Submit #868962: dromara lamp-cloud Releases20260625 path traversal (by Ku4D3)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.