CVE-2026-22786
Path Traversal in Gin-vue-admin Breakpoint Upload Allows Arbitrary File Write
Publication date: 2026-01-12
Last updated on: 2026-03-12
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gin-vue-admin_project | gin-vue-admin | to 2.8.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22786 is a path traversal vulnerability in Gin-vue-admin versions up to 2.8.7, specifically in the breakpoint resume upload functionality. The vulnerability exists because the MakeFile function accepts a fileName parameter via an API endpoint and concatenates it directly with a base directory path without validating for directory traversal sequences like '../'. This allows an attacker with file upload privileges to upload files to arbitrary directories on the server by exploiting this lack of validation. [2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with file upload privileges to create or overwrite arbitrary files anywhere on the server. This can lead to overwriting configuration files, uploading malicious code, and potentially achieving remote code execution, which compromises the security and integrity of the affected system. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
You can detect this vulnerability by monitoring for suspicious file upload activity to the /fileUploadAndDownload/breakpointContinueFinish API endpoint, especially requests containing directory traversal sequences like '../' in the fileName parameter. Network traffic inspection tools or web application firewalls can be configured to log or block such attempts. Additionally, checking server logs for file creations outside the expected ./fileDir/ directory may indicate exploitation attempts. Specific commands depend on your environment, but for example, using grep on server logs to find suspicious file paths: grep -r '../' /path/to/logs or using curl to test the endpoint with a traversal payload: curl -X POST -F "fileName=../../../tmp/malicious.txt" http://yourserver/fileUploadAndDownload/breakpointContinueFinish [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting or disabling file upload privileges to only trusted users, especially those with role ID 888 (super administrator). Monitor and block requests to the /fileUploadAndDownload/breakpointContinueFinish endpoint that contain directory traversal sequences in the fileName parameter. Applying input validation or sanitization on the fileName parameter to prevent directory traversal is critical. Since no official patch is currently available, consider upgrading to version 2.8.8 or later once released, as it includes filename and path validity checks addressing this issue. Additionally, review and harden server permissions to limit the impact of arbitrary file writes. [1, 2]