Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.81% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-101894High confidence
@xhmikosr/decompress: Path traversal via symlink chain
XhmikosR · decompress
Official source article: GitHub GHSA-HRH2-VP3X-79XF ↗. Check the applicable product and release in the original source.
9.1CriticalCVSS 3.1
Within 72 hours
Fix not verifiedCritical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs XhmikosR decompress and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npm@xhmikosr/decompress | >= 11.0.0, <= 11.1.3 | 11.1.4 | GitHub advisory ↗upstream repository advisory · 29 Sep 2026 |
| npm@xhmikosr/decompress | <= 10.2.1 | 10.2.2 | GitHub advisory ↗upstream repository advisory · 29 Sep 2026 |
| npm@xhmikosr/decompress | SEMVER: introduced 11.0.0; fixed 11.1.4 | 11.1.4 | OSV record ↗aggregator derived · 30 Sep 2026 |
| npm@xhmikosr/decompress | SEMVER: introduced 0; fixed 10.2.2 | 10.2.2 | OSV record ↗aggregator derived · 30 Sep 2026 |
| npmdecompress | <= 4.2.1 | Not stated | GitHub advisory ↗upstream repository advisory · 29 Sep 2026 |
| npmdecompress | SEMVER: introduced 0; last affected 4.2.1 | Not stated | OSV record ↗aggregator derived · 30 Sep 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-101894 · CSAF 2.0 · revision 2 · interimSUSE Product Security TeamCVE-2026-101894
The vendor explicitly identifies these products as affected by this CVE.
- pgadmin4 as component of SUSE Linux Enterprise Desktop 15 SP7
- pgadmin4-doc as component of SUSE Linux Enterprise Desktop 15 SP7
- pgadmin4-web as component of SUSE Linux Enterprise Desktop 15 SP7
- system-user-pgadmin as component of SUSE Linux Enterprise Desktop 15 SP7
- nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- Summary
- The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
- Remediation
- No remediation text is recorded.
Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded.
Fix not verified01
What, why and how
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
What
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
What
The decompress package for Node.js extracts archives. Prior to 10.2.2 and 11.1.4, the default decompress(input, output) API relies on lexical containment checks that do not account for the kernel following a planted symlink chain. An attacker can supply a crafted archive containing chained symlink entries so that a later entry resolves outside the output directory. This allows files outside output to be read or written, and overwriting startup scripts or configuration can lead to remote code execution. The maintained @xhmikosr/decompress package is fixed in 10.2.2 and 11.1.4, but the separately affected unmaintained decompress package remains unpatched through 4.2.1. This vulnerability results from a bypass of the incomplete hardening for CVE-2026-53486. @xhmikosr/decompress is fixed in versions 10.2.2 and 11.1.4.
Why
Attacker-controlled path data is not constrained to the intended directory before the application accesses a file.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-22 ↗
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'). 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.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- pgadmin4 as component of SUSE Linux Enterprise Desktop 15 SP7
- pgadmin4-doc as component of SUSE Linux Enterprise Desktop 15 SP7
- pgadmin4-web as component of SUSE Linux Enterprise Desktop 15 SP7
- system-user-pgadmin as component of SUSE Linux Enterprise Desktop 15 SP7
- nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP1
- nodejs10 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs10-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs10-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs12 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs12-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs12-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs8 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs8-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- nodejs8-docs as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- npm10 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- npm12 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- npm8 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- pgadmin4 as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- pgadmin4-doc as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- pgadmin4-web as component of SUSE Linux Enterprise High Performance Computing 15 SP2
- and 270 more
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 28 Sept 2026 · Last source change 28 Sept 2026, 17:39 UTC · CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-29
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-88365
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-88365 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-88365"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.