CVE-2026-93992 GopeedLab CVE debrief

Who should care

Defenders responsible for Gopeed installations, especially those using AutoExtract functionality, should assess exposure and prioritize remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify and remediate this vulnerability to prevent potential exploitation. System owners and IT teams should review the vulnerability details and take appropriate actions to secure their deployments

Why it matters

CVE-2026-93992 is a path traversal vulnerability in Gopeed that allows attackers to write arbitrary files outside the extraction directory when AutoExtract is enabled, potentially disrupting system integrity and availability.

• Potential for attackers to write arbitrary files outside the extraction directory
• Possible disruption of system integrity and availability
• Need for verification of Gopeed installations and AutoExtract usage
• Priority for remediation to prevent potential exploitation

Technical summary

The vulnerability is caused by a path traversal issue in the archive extraction functionality of Gopeed, allowing attackers to write arbitrary files outside the extraction directory when AutoExtract is enabled. This occurs due to insufficient validation of archive entries containing directory traversal sequences. The vulnerability has a CVSS score of 7 and is classified as HIGH severity. Technical details indicate that the vulnerability affects Gopeed versions up to 2.0.0-beta.3. Affected systems may face potential disruption of system integrity and availability.

Defensive priority

Defenders should prioritize verifying and remediating this vulnerability in Gopeed installations, especially where AutoExtract is enabled.

Recommended defensive actions

• Verify Gopeed installations and assess exposure to AutoExtract functionality
• Remediate vulnerable Gopeed installations by updating to a fixed version
• Monitor for potential exploitation attempts targeting this vulnerability
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is described in the CVE and NVD records. Additional details are provided by source references, including GitHub repository and advisory links. However, the exact scope of affected systems and potential impact on system integrity and availability require further verification. Defenders should review the official CVE record and NVD details for accurate information. Evidence limits and potential unknowns in affected scope should be considered during verification and remediation efforts.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.