peerigon unzip-crx/unzip-crx-3 up to 0.2.0 Archive Extraction dist/index.js unzip destination path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.0 | $0-$5k | 0.66+ |
Summary
A vulnerability identified as problematic has been detected in peerigon unzip-crx and unzip-crx-3 up to 0.2.0. This impacts the function unzip of the file dist/index.js of the component Archive Extraction. The manipulation of the argument destination leads to path traversal.
This vulnerability is referenced as CVE-2026-78638. The attack can only be performed from a local environment. Furthermore, an exploit is available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in peerigon unzip-crx and unzip-crx-3 up to 0.2.0. It has been rated as problematic. This issue affects the function unzip of the file dist/index.js of the component Archive Extraction. The manipulation of the argument destination 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 integrity.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-78638. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.
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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
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: Partially
Local: Yes
Remote: No
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/24/2026 VulDB entry created08/25/2026 Advisory disclosed
08/25/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 19
Status: Not defined
CVE: CVE-2026-78638 (🔒)
GCVE (CVE): GCVE-0-2026-78638
GCVE (VulDB): GCVE-100-394865
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/25/2026 01:08Changes: 08/25/2026 01:08 (60)
Complete: 🔍
Submitter: Classif1ed_mick
Cache ID: 216::103
Submit
Accepted
- Submit #886400: peerigon / unzip-crx-3 (open source, unmaintained) unzip-crx-3 (npm) CRX/ZIP extraction library <=0.2.0 Path Traversal (by github.com)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.