NVD / CVE Program· CNA GitHub_M

CVE-2021-32803: Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning

Noroxi assessment

Priority: Monitor (action score 34/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 7.7% (FIRST EPSS); higher than 94.6% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: nodejs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7, 1:12.22.5-1.module_el8.5.0+85+79a7b441; nodejs-devel (AlmaLinux:8) 1:12.22.5-1.module_el8.5.0+85+79a7b441, 1:12.22.5-1.module_el8.4.0+2529+af52a4c7; nodejs-docs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7.
Mentioned 4 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to nodejs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7, 1:12.22.5-1.module_el8.5.0+85+79a7b441; nodejs-devel (AlmaLinux:8) 1:12.22.5-1.module_el8.5.0+85+79a7b441, 1:12.22.5-1.module_el8.4.0+2529+af52a4c7; nodejs-docs (AlmaLinux:8) 1:12.22.5-1.module_el8.4.0+2529+af52a4c7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The npm package "tar" (aka node-tar) before versions 6.1.2, 5.0.7, 4.4.15, and 3.2.3 has an arbitrary File Creation/Overwrite vulnerability via insufficient symlink protection. `node-tar` aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary `stat` calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory. This order of operations resulted in the directory being created and added to the `node-tar` directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where `node-tar` checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass `node-tar` symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.3, 4.4.15, 5.0.7 and 6.1.2.

HighCVSS 8.1 · v3.1—No exploit Fix available

Published: Aug 3, 2021
Updated: Jun 16, 2026
EPSS: 7.7% · 94th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 32 / 40 · 8.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 2 / 30 · 7.7%

CNA vs NVD score

NVD: 8.1
CNA · GitHub_M: 8.2; 0.1 point gap

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
tar project	tar	cpe:2.3:a:tar_project:tar
oracle	graalvm	cpe:2.3:a:oracle:graalvm
siemens	sinec infrastructure network services	cpe:2.3:a:siemens:sinec_infrastructure_network_services

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

oracle graalvm20.3.3
oracle graalvm21.2.0
siemens sinec infrastructure network servicesbefore 1.0.1.1
tar project tarbefore 3.2.3
tar project tar6.0.0 and later · before 6.1.2
tar project tar4.0.0 and later · before 4.4.15
tar project tar5.0.0 and later · before 5.0.7

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

npm node-tar
- < 3.2.3, >= 4.0.0, < 4.4.15, >= 5.0.0, < 5.0.7, >= 6.0.0, < 6.1.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

+63

Same product

tar project: all records

Other highest-scoring records for the same primary product.

CVE-2021-32804Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization
37Monitor
CVE-2018-20990An issue was discovered in the tar crate before 0.4.16 for Rust.
31Monitor
CVE-2021-38511An issue was discovered in the tar crate before 0.4.36 for Rust.
30Monitor

Published before and after this one in the same product

Later →CVE-2026-33056Mar 20, 2026 · tar-rs: unpack_in can chmod arbitrary directories by following symlinks
20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
almalinux:nodejs	1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-devel	1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-docs	1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-full-i18n	1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-nodemon	2.0.3-1.module_el8.4.0+2521+c668cc9f · AlmaLinux:8	Package registry (OSV)
almalinux:nodejs-packaging	17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8	Package registry (OSV)
almalinux:npm	1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8	Package registry (OSV)
alpine:tar	0 · Alpine:v3.16	Package registry (OSV)
debian:node-tar	6.1.7+~cs11.3.10-1 · Debian:12	Package registry (OSV)
npm:tar	3.2.3	Package registry (OSV)
npm:tar	4.4.15	Package registry (OSV)
npm:tar	5.0.7	Package registry (OSV)
npm:tar	6.1.2	Package registry (OSV)
opensuse:nodejs10	10.24.1-150000.1.44.1 · openSUSE:Leap 15.3	Package registry (OSV)
opensuse:nodejs12	12.22.10-4.29.3 · openSUSE:Leap 15.3	Package registry (OSV)
opensuse:nodejs14	14.19.0-15.27.1 · openSUSE:Leap 15.3	Package registry (OSV)
opensuse:nodejs8	8.17.0-10.19.2 · openSUSE:Leap 15.3	Package registry (OSV)
red hat:rh-nodejs12-nodejs	0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs12-nodejs-debuginfo	0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs12-nodejs-devel	0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs12-nodejs-docs	0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs12-nodejs-nodemon	0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs12-npm	0:6.14.14-12.22.5.1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-nodejs	0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-nodejs-debuginfo	0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-nodejs-devel	0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-nodejs-docs	0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-nodejs-nodemon	0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
red hat:rh-nodejs14-npm	0:6.14.14-14.17.5.1.el7 · Red Hat:rhel_software_collections:3::el7	Package registry (OSV)
rocky linux:nodejs	1:12.22.5-1.module+el8.4.0+647+e905fa21 · Rocky Linux:8	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

npm/node-tarcommit 9dbdeb6

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-22-0215 · Mar 11, 2022(Siemens Güvenlik Bildirimi)
TR-21-0949 · Nov 25, 2021(IBM Güvenlik Bülteni Yayınladı)
TR-21-0921 · Nov 16, 2021(IBM Güvenlik Bülteni Yayınladı)
TR-21-0779 · Sep 28, 2021(RedHat Güvenlik Güncellemesi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: None
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

nvd-primary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Ecosystem	Package	Affected range	Fix
AlmaLinux:8	nodejs	before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7	1:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8	nodejs	before 1:12.22.5-1.module_el8.5.0+85+79a7b441	1:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8	nodejs-devel	before 1:12.22.5-1.module_el8.5.0+85+79a7b441	1:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8	nodejs-devel	before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7	1:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8	nodejs-docs	before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7	1:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8	nodejs-full-i18n	before 1:12.22.5-1.module_el8.5.0+85+79a7b441	1:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8	nodejs-full-i18n	before 1:12.22.5-1.module_el8.4.0+2529+af52a4c7	1:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8	nodejs-nodemon	before 2.0.3-1.module_el8.4.0+2521+c668cc9f	2.0.3-1.module_el8.4.0+2521+c668cc9f
AlmaLinux:8	nodejs-packaging	before 17-3.module_el8.4.0+2521+c668cc9f	17-3.module_el8.4.0+2521+c668cc9f
AlmaLinux:8	nodejs-packaging	before 23-3.module_el8.4.0+2522+3bd42762	23-3.module_el8.4.0+2522+3bd42762
AlmaLinux:8	nodejs-packaging	before 23-3.module_el8.5.0+254+b4526b16	23-3.module_el8.5.0+254+b4526b16
AlmaLinux:8	nodejs-packaging	before 17-3.module_el8.3.0+2023+d2377ea3	17-3.module_el8.3.0+2023+d2377ea3
AlmaLinux:8	nodejs-packaging	before 17-3.module_el8.4.0+2224+b07ac28e	17-3.module_el8.4.0+2224+b07ac28e
AlmaLinux:8	npm	before 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441	1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441
AlmaLinux:8	npm	before 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7	1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7
Debian:12	node-tar	before 6.1.7+~cs11.3.10-1	6.1.7+~cs11.3.10-1
npm	tar	from 3.0.0 · before 3.2.3	3.2.3
npm	tar	from 4.0.0 · before 4.4.15	4.4.15
npm	tar	from 5.0.0 · before 5.0.7	5.0.7
npm	tar	from 6.0.0 · before 6.1.2	6.1.2
openSUSE:Leap 15.3	nodejs10	before 10.24.1-150000.1.44.1	10.24.1-150000.1.44.1
openSUSE:Leap 15.3	nodejs12	before 12.22.10-4.29.3	12.22.10-4.29.3
openSUSE:Leap 15.3	nodejs14	before 14.19.0-15.27.1	14.19.0-15.27.1
openSUSE:Leap 15.3	nodejs8	before 8.17.0-10.19.2	8.17.0-10.19.2