Decap Server Local Proxy Containment Guard path traversal

Summaryinfo

A vulnerability identified as critical has been detected in Decap Server. This affects an unknown function of the component Local Proxy Containment Guard. The manipulation leads to path traversal. This vulnerability is referenced as CVE-2026-92812. Remote exploitation of the attack is possible. No exploit is available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Decap Server (affected version not known). It has been rated as critical. This issue affects some unknown functionality of the component Local Proxy Containment Guard. The manipulation 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. The summary by CVE is:

decap-server contains a path traversal vulnerability in the local proxy containment guard that uses plain string prefix comparison without path separator validation. Attackers can access sibling directories whose names begin with the repository directory name to read, write, or delete files outside the intended repository root.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-92812 since 09/16/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.

Applying the patch 11f35405cd1a1d1216e97b890173f46436752019 is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-81070). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Decap

Name

• Server

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion