CVE-2026-78638 peerigon CVE debrief

Who should care

Defenders responsible for local development environments using unzip-crx or unzip-crx-3 should assess the risk of path traversal attacks and verify the presence of vulnerable versions.

Why it matters

Defenders should prioritize verifying the presence of vulnerable unzip-crx versions in their local development environments and assess the risk of path traversal attacks.

• Path traversal attacks can lead to unauthorized access to sensitive files
• Local exploitation requires careful manipulation of the destination argument
• Verification of vulnerable versions is necessary to assess risk

Technical summary

The unzip function in dist/index.js of peerigon unzip-crx and unzip-crx-3 up to 0.2.0 is vulnerable to path traversal attacks when manipulating the destination argument. This allows attackers to write files to arbitrary locations, potentially leading to unauthorized access or data corruption. The attack can only be executed locally, and defenders should prioritize verifying the presence of vulnerable unzip-crx versions in their local development environments and assess the risk of path traversal attacks. The vulnerability has been publicly disclosed, and defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Defensive priority

Defenders should prioritize verifying the presence of vulnerable unzip-crx versions in their local development environments and assess the risk of path traversal attacks.

Recommended defensive actions

• Verify the presence of vulnerable unzip-crx versions in local development environments
• Assess the risk of path traversal attacks
• Consider updating to a fixed version if available
• 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 CVE record and NVD entry provide details about the vulnerability, but the scope of affected versions and potential impact require further verification. The vulnerability has been publicly disclosed and may be used by attackers. There is no information on whether the project has responded to the issue report yet. Defenders should verify the presence of vulnerable unzip-crx versions in their local development environments and assess the risk of path traversal attacks.

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.