Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2021-32804: Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization

Noroxi assessment

Priority: Monitor (action score 37/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 15% (FIRST EPSS); higher than 96.7% 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 3 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.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.

HighCVSS 8.1 · v3.1—Proof of concept Fix available
Published
Aug 3, 2021
Updated
Jun 16, 2026
EPSS
15.0% · 96th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
5 / 30 · 15.0%

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
  • Proof of concept exists, no weaponized module
  • A fix has been released

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

Follow CVE-2021-32804

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

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.

VendorProduct
tar projecttar
oraclegraalvm
siemenssinec 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.2
  • tar project tar6.0.0 and later · before 6.1.1
  • tar project tar4.0.0 and later · before 4.4.14
  • tar project tar5.0.0 and later · before 5.0.6

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.2, >= 4.0.0, < 4.4.14, >= 5.0.0, < 5.0.6, >= 6.0.0, < 6.1.1affected

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8nodejsbefore 1:12.22.5-1.module_el8.4.0+2529+af52a4c71:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8nodejsbefore 1:12.22.5-1.module_el8.5.0+85+79a7b4411:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8nodejs-develbefore 1:12.22.5-1.module_el8.5.0+85+79a7b4411:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8nodejs-develbefore 1:12.22.5-1.module_el8.4.0+2529+af52a4c71:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8nodejs-docsbefore 1:12.22.5-1.module_el8.4.0+2529+af52a4c71:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8nodejs-full-i18nbefore 1:12.22.5-1.module_el8.4.0+2529+af52a4c71:12.22.5-1.module_el8.4.0+2529+af52a4c7
AlmaLinux:8nodejs-full-i18nbefore 1:12.22.5-1.module_el8.5.0+85+79a7b4411:12.22.5-1.module_el8.5.0+85+79a7b441
AlmaLinux:8nodejs-nodemonbefore 2.0.3-1.module_el8.4.0+2521+c668cc9f2.0.3-1.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.5.0+254+b4526b1623-3.module_el8.5.0+254+b4526b16
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2224+b07ac28e17-3.module_el8.4.0+2224+b07ac28e
AlmaLinux:8nodejs-packagingbefore 23-3.module_el8.4.0+2522+3bd4276223-3.module_el8.4.0+2522+3bd42762
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.4.0+2521+c668cc9f17-3.module_el8.4.0+2521+c668cc9f
AlmaLinux:8nodejs-packagingbefore 17-3.module_el8.3.0+2023+d2377ea317-3.module_el8.3.0+2023+d2377ea3
AlmaLinux:8npmbefore 1:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b4411:6.14.14-1.12.22.5.1.module_el8.5.0+85+79a7b441
AlmaLinux:8npmbefore 1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c71:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7
Debian:12node-tarbefore 6.1.7+~cs11.3.10-16.1.7+~cs11.3.10-1
npmtarfrom 4.0.0 · before 4.4.144.4.14
npmtarfrom 5.0.0 · before 5.0.65.0.6
npmtarfrom 6.0.0 · before 6.1.16.1.1
npmtarbefore 3.2.23.2.2
openSUSE:Leap 15.3nodejs10before 10.24.1-150000.1.44.110.24.1-150000.1.44.1
openSUSE:Leap 15.3nodejs12before 12.22.10-4.29.312.22.10-4.29.3
openSUSE:Leap 15.3nodejs14before 14.19.0-15.27.114.19.0-15.27.1
openSUSE:Leap 15.3nodejs8before 8.17.0-10.19.28.17.0-10.19.2

+63

Other highest-scoring records for the same primary product.

  • CVE-2021-32803Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning
    34Monitor
  • 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 / packageFixed versionSource
almalinux:nodejs1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-devel1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-docs1:12.22.5-1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-full-i18n1:12.22.5-1.module_el8.5.0+85+79a7b441 · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-nodemon2.0.3-1.module_el8.4.0+2521+c668cc9f · AlmaLinux:8Package registry (OSV)
almalinux:nodejs-packaging17-3.module_el8.4.0+2224+b07ac28e · AlmaLinux:8Package registry (OSV)
almalinux:npm1:6.14.14-1.12.22.5.1.module_el8.4.0+2529+af52a4c7 · AlmaLinux:8Package registry (OSV)
alpine:tar0 · Alpine:v3.16Package registry (OSV)
debian:node-tar6.1.7+~cs11.3.10-1 · Debian:12Package registry (OSV)
npm:tar3.2.2Package registry (OSV)
npm:tar4.4.14Package registry (OSV)
npm:tar5.0.6Package registry (OSV)
npm:tar6.1.1Package registry (OSV)
opensuse:nodejs1010.24.1-150000.1.44.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs1212.22.10-4.29.3 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs1414.19.0-15.27.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:nodejs88.17.0-10.19.2 · openSUSE:Leap 15.3Package registry (OSV)
red hat:rh-nodejs12-nodejs0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-debuginfo0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-devel0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-docs0:12.22.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-nodejs-nodemon0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs12-npm0:6.14.14-12.22.5.1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs-debuginfo0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs-devel0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs-docs0:14.17.5-1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-nodejs-nodemon0:2.0.3-5.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
red hat:rh-nodejs14-npm0:6.14.14-14.17.5.1.el7 · Red Hat:rhel_software_collections:3::el7Package registry (OSV)
rocky linux:nodejs1:12.22.5-1.module+el8.4.0+647+e905fa21 · Rocky Linux:8Package registry (OSV)

+8

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12021-08-31

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.

  1. Published
  2. First PoC+27 d
  3. TodayNov 4, 2026+1919 d

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.

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.

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

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.

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

Vulnerable

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

Fixed

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

Change log

  1. Fix✗ → ✓

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

References

All records