{"id":"CVE-2021-37713","aliases":["ALPINE-CVE-2021-37713","BELL-CVE-2021-37713","CLSA-2026-1773188129","CLSA-2026-1773620217","CLSA-2026-1774484514","CLSA-2026-1775176107","CLSA-2026-1792164662","CLSA-2026-1792369404","CLSA-2026-1793790160","EUVD-2021-1573","GHSA-5955-9wpr-37jh","MGASA-2021-0463","ROOT-APP-NPM-CVE-2021-37713","SUSE-SU-2021:3886-1","SUSE-SU-2021:3940-1","SUSE-SU-2021:3964-1","SUSE-SU-2022:0101-1","openSUSE-SU-2021:1552-1","openSUSE-SU-2021:1574-1","openSUSE-SU-2021:3940-1","openSUSE-SU-2021:3964-1","openSUSE-SU-2024:11616-1"],"status":"published","title":"Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","severity":{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.01273,"percentile":0.70126,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-22"],"published":"2021-08-31T16:05:05Z","modified":"2026-11-04T14:45:04Z","fixes":[{"ecosystem":"npm","package":"tar","fixed_in":["4.4.18","5.0.10","6.1.9"],"sources":["ghsa","osv"]},{"ecosystem":"Alpine:v3.11","package":"nodejs","fixed_in":["12.22.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.12","package":"nodejs","fixed_in":["12.22.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.13","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.14","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.15","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.16","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.17","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.18","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.19","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.20","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.21","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.22","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.23","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.24","package":"nodejs","fixed_in":["14.17.6-r0"],"sources":["osv"]},{"ecosystem":"TuxCare:npm","package":"tar","fixed_in":["4.4.6-tuxcare.1"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"tar","fixed_in":["4.4.13-aikido.1"],"sources":["osv"]},{"ecosystem":"Root:npm","package":"@rootio/tar","fixed_in":["4.4.13-root.io.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.18"}]}]},{"source":"ghsa","ecosystem":"npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.0"},{"fixed":"5.0.10"}]}]},{"source":"ghsa","ecosystem":"npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}]},{"source":"osv","ecosystem":"Alpine:v3.11","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.12","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.13","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.14","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.15","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.16","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.17","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.18","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.19","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.20","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.21","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.22","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.23","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.24","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-r0"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.2.2-tuxcare.0"},{"fixed":"2.2.2-tuxcare.1"}]}],"versions":["2.2.2"],"bundled":7},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.3-tuxcare.0"},{"fixed":"1.0.3-tuxcare.1"}]}],"versions":["1.0.3"],"bundled":4},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.1-tuxcare.0"},{"fixed":"2.1.1-tuxcare.1"}]}],"versions":["2.1.1"],"bundled":5},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.2-tuxcare.0"},{"fixed":"6.0.2-tuxcare.3"}]}],"versions":["6.0.2","6.0.2-tuxcare.1","6.0.2-tuxcare.2"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.6-tuxcare.0"},{"fixed":"6.1.6-tuxcare.1"}]}],"versions":["6.1.6"],"bundled":8},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.0-tuxcare.0"},{"fixed":"6.1.0-tuxcare.2"}]}],"versions":["6.1.0","6.1.0-tuxcare.1"],"bundled":9},{"source":"osv","ecosystem":"TuxCare:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.4.6-tuxcare.0"},{"fixed":"4.4.6-tuxcare.1"}]}],"versions":["4.4.6"]},{"source":"osv","ecosystem":"npm","package":"tar","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.4.18"}]}]},{"source":"osv","ecosystem":"npm","package":"tar","ranges":[{"type":"SEMVER","events":[{"introduced":"5.0.0"},{"fixed":"5.0.10"}]}]},{"source":"osv","ecosystem":"npm","package":"tar","ranges":[{"type":"SEMVER","events":[{"introduced":"6.0.0"},{"fixed":"6.1.9"}]}]},{"source":"osv","ecosystem":"Mageia:8","package":"nodejs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.17.6-1.mga8"}]}],"bundled":9},{"source":"osv","ecosystem":"Root:npm","package":"tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.13-aikido.1"}]}]},{"source":"osv","ecosystem":"Root:npm","package":"@rootio/tar","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.4.13-root.io.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-6.18.2"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP2","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.7-4.22.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP3","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.7-4.22.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP2","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-15.21.2"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 15 SP3","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-15.21.2"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Web and Scripting 12","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.9-1.38.1"}]}],"bundled":11},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-lp152.17.1"}]}],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Leap 15.2","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.7-lp152.3.21.1"}]}],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"nodejs12","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.22.7-4.22.1"}]}],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Leap 15.3","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-15.21.2"}]}],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"nodejs14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"14.18.1-1.1"}]}],"bundled":5}],"products":[{"vendor":"isaacs","product":"node-tar"},{"vendor":"npm","product":"node-tar"},{"vendor":"npmjs","product":"tar"},{"vendor":"oracle","product":"graalvm"},{"vendor":"siemens","product":"sinec_infrastructure_network_services"}],"references":[{"url":"https://www.npmjs.com/package/tar","tags":["x_refsource_MISC","x_transferred","Product","Third Party Advisory","advisory","web"]},{"url":"https://github.com/npm/node-tar/security/advisories/GHSA-5955-9wpr-37jh","tags":["x_refsource_CONFIRM","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://www.oracle.com/security-alerts/cpuoct2021.html","tags":["x_refsource_MISC","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf","tags":["x_refsource_CONFIRM","x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-37713","tags":["advisory"]},{"url":"https://github.com/isaacs/node-tar/commit/52b09e309bcae0c741a7eb79a17ef36e7828b946","tags":["web"]},{"url":"https://github.com/isaacs/node-tar/commit/82eac952f7c10765969ed464e549375854b26edc","tags":["web"]},{"url":"https://github.com/isaacs/node-tar/commit/875a37e3ec031186fc6599f6807341f56c584598","tags":["web"]},{"url":"https://github.com/advisories/GHSA-5955-9wpr-37jh"},{"url":"https://security.alpinelinux.org/vuln/CVE-2021-37713","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2021-37713","tags":["advisory"]},{"url":"https://github.com/npm/node-tar","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2021-0463.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=29365","tags":["report"]},{"url":"https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases/","tags":["web"]},{"url":"https://nodejs.org/en/blog/release/v14.17.5/","tags":["web"]},{"url":"https://nodejs.org/en/blog/vulnerability/aug-2021-security-releases2/","tags":["web"]},{"url":"https://nodejs.org/en/blog/release/v14.17.6/","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20213886-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1190053","tags":["report"]},{"url":"https://bugzilla.suse.com/1190054","tags":["report"]},{"url":"https://bugzilla.suse.com/1190055","tags":["report"]},{"url":"https://bugzilla.suse.com/1190056","tags":["report"]},{"url":"https://bugzilla.suse.com/1190057","tags":["report"]},{"url":"https://bugzilla.suse.com/1191601","tags":["report"]},{"url":"https://bugzilla.suse.com/1191602","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22959","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22960","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37713","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-39134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-39135","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20213940-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2021/suse-su-20213964-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2022/suse-su-20220101-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1194511","tags":["report"]},{"url":"https://bugzilla.suse.com/1194512","tags":["report"]},{"url":"https://bugzilla.suse.com/1194513","tags":["report"]},{"url":"https://bugzilla.suse.com/1194514","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2021-44531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-44532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-44533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21824","tags":["web"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/INKZHV64GX7LRVL3YYOERQLU3B3U47QD/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/OZ6MU5ASKOGKZBGVKFFXVB64PMZRVEPX/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/LB7JXCGGW7EKOPAS4IDMUQPYHXS3ZUZA/","tags":["advisory"]},{"url":"https://lists.opensuse.org/archives/list/security-announce@lists.opensuse.org/thread/EB6I33SJCMQ2K7LAKKPS54HRXSB7FQXG/","tags":["advisory"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2021-37713","title":"Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","status":"published","published":"2021-08-31T16:50:09Z","modified":"2024-08-04T01:23:01.533Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:32:58.359368Z"}],"euvd":[{"id":"EUVD-2021-1573","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","status":"published","published":"2021-08-31T16:50:09Z","modified":"2024-08-04T01:23:01Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"updated_at":"2026-11-03T03:24:27.254804Z"}],"ghsa":[{"id":"GHSA-5955-9wpr-37jh","title":"Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization","description":"### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory.\n\nThis logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`.  If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory.\n\nAdditionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path.\n\nThis only affects users of `node-tar` on Windows systems.\n\n### Patches\n\n4.4.18 || 5.0.10 || 6.1.9\n\n### Workarounds\n\nThere is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does.\n\nUsers are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.\n\n### Fix\n\nThe fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not \"absolute\".\n\nAdditionally, a path starting with a drive letter and then two dots, like `c:../`, would bypass the check for `..` path portions.  This is checked properly in the patched versions.\n\nFinally, a defense in depth check is added, such that if the `entry.absolute` is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped.  Currently, it is believed that this check is redundant, but it did catch some oversights in development.\n","status":"published","published":"2021-08-31T16:05:05Z","modified":"2023-11-29T22:26:30Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:37:23.843848Z"}],"nvd":[{"id":"CVE-2021-37713","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","status":"published","published":"2021-08-31T17:15:08.087Z","modified":"2026-06-17T04:01:02.383Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high","assessor":"secondary"},{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":4.4,"vector":"AV:L/AC:M/Au:N/C:P/I:P/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T14:06:57.67549Z"}],"osv":[{"id":"ALPINE-CVE-2021-37713","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","status":"published","published":"2021-08-31T17:15:08.087Z","modified":"2026-10-23T17:17:56.204750672Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:27:48.646074Z"},{"id":"BELL-CVE-2021-37713","title":"CVE-2021-37713 does not affect BellSoft software","status":"withdrawn","published":"2023-08-31T12:14:33.35621Z","modified":"2026-02-18T07:38:25.024415Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:16.5265Z"},{"id":"CVE-2021-37713","description":"The npm package \"tar\" (aka node-tar) before versions 4.4.18, 5.0.10, and 6.1.9 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory. This logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`. If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory. Additionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path. This only affects users of `node-tar` on Windows systems. These issues were addressed in releases 4.4.18, 5.0.10 and 6.1.9. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. There is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does. Users are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.","status":"published","published":"2021-08-31T17:15:08.087Z","modified":"2026-10-24T10:50:42.458766706Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:20.434873Z"},{"id":"GHSA-5955-9wpr-37jh","title":"Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization","description":"### Impact\n\nArbitrary File Creation, Arbitrary File Overwrite, Arbitrary Code Execution\n\nnode-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain `..` path portions, and resolving the sanitized paths against the extraction target directory.\n\nThis logic was insufficient on Windows systems when extracting tar files that contained a path that was not an absolute path, but specified a drive letter different from the extraction target, such as `C:some\\path`.  If the drive letter does not match the extraction target, for example `D:\\extraction\\dir`, then the result of `path.resolve(extractionDirectory, entryPath)` would resolve against the current working directory on the `C:` drive, rather than the extraction target directory.\n\nAdditionally, a `..` portion of the path could occur immediately after the drive letter, such as `C:../foo`, and was not properly sanitized by the logic that checked for `..` within the normalized and split portions of the path.\n\nThis only affects users of `node-tar` on Windows systems.\n\n### Patches\n\n4.4.18 || 5.0.10 || 6.1.9\n\n### Workarounds\n\nThere is no reasonable way to work around this issue without performing the same path normalization procedures that node-tar now does.\n\nUsers are encouraged to upgrade to the latest patched versions of node-tar, rather than attempt to sanitize paths themselves.\n\n### Fix\n\nThe fixed versions strip path roots from all paths prior to being resolved against the extraction target folder, even if such paths are not \"absolute\".\n\nAdditionally, a path starting with a drive letter and then two dots, like `c:../`, would bypass the check for `..` path portions.  This is checked properly in the patched versions.\n\nFinally, a defense in depth check is added, such that if the `entry.absolute` is outside of the extraction taret, and we are not in preservePaths:true mode, a warning is raised on that entry, and it is skipped.  Currently, it is believed that this check is redundant, but it did catch some oversights in development.\n","status":"published","published":"2021-08-31T16:05:05Z","modified":"2026-07-08T06:28:41.552506062Z","cvss":[{"version":"3.1","score":8.2,"vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","level":"high"}],"cwes":["CWE-22"],"updated_at":"2026-11-02T15:46:38.213481Z"},{"id":"CLSA-2026-1773188129","title":"TuxCare security update for tar (7 CVEs)","description":"TuxCare rebuilt tar to address 7 CVEs. Fixed in 2.2.2-tuxcare.1.","status":"published","published":"2026-08-04T14:52:12Z","modified":"2026-10-15T09:47:27.769618678Z","updated_at":"2026-11-02T15:43:43.249928Z"},{"id":"CLSA-2026-1773620217","title":"TuxCare security update for tar (4 CVEs)","description":"TuxCare rebuilt tar to address 4 CVEs. Fixed in 1.0.3-tuxcare.1.","status":"published","published":"2026-08-04T14:52:12Z","modified":"2026-10-23T19:28:13.603540691Z","updated_at":"2026-11-02T15:43:43.621843Z"},{"id":"CLSA-2026-1774484514","title":"TuxCare security update for tar (5 CVEs)","description":"TuxCare rebuilt tar to address 5 CVEs. Fixed in 2.1.1-tuxcare.1.","status":"published","published":"2026-08-04T14:52:15Z","modified":"2026-10-15T09:47:04.625520498Z","updated_at":"2026-11-02T15:43:43.621843Z"},{"id":"CLSA-2026-1775176107","title":"TuxCare security update for tar (2 CVEs)","description":"TuxCare rebuilt tar to address 2 CVEs. Fixed in 6.0.2-tuxcare.3.","status":"published","published":"2026-08-04T14:52:20Z","modified":"2026-10-15T09:45:43.101572732Z","updated_at":"2026-11-02T15:43:44.009773Z"},{"id":"CLSA-2026-1792164662","title":"TuxCare security update for tar (8 CVEs)","description":"TuxCare rebuilt tar to address 8 CVEs. Fixed in 6.1.6-tuxcare.1.","status":"published","published":"2026-10-16T15:31:02Z","modified":"2026-10-16T16:30:59.349131841Z","updated_at":"2026-11-02T15:43:51.747192Z"},{"id":"CLSA-2026-1792369404","title":"TuxCare security update for tar (9 CVEs)","description":"TuxCare rebuilt tar to address 9 CVEs. Fixed in 6.1.0-tuxcare.2.","status":"published","published":"2026-10-19T00:23:24Z","modified":"2026-10-27T01:58:02.886782149Z","updated_at":"2026-11-02T15:43:53.353888Z"},{"id":"CLSA-2026-1793790160","title":"TuxCare security update for tar (1 CVE)","description":"TuxCare rebuilt tar to address 1 CVE. Fixed in 4.4.6-tuxcare.1.","status":"published","published":"2026-11-04T12:02:41Z","modified":"2026-11-04T14:45:04.29857321Z","updated_at":"2026-11-04T15:03:54.132276Z"},{"id":"MGASA-2021-0463","title":"Updated nodejs packages fix security vulnerability","description":"Multiple security fixes for nodejs. See references for details\n","status":"published","published":"2021-10-06T19:41:56Z","modified":"2026-04-16T04:41:26.552726206Z","updated_at":"2026-11-02T15:49:41.849028Z"},{"id":"openSUSE-SU-2021:1552-1","title":"Security update for nodejs14","description":"This update for nodejs14 fixes the following issues:\n\nnodejs14 was updated to 14.18.1:\n\n* deps: update llhttp to 2.1.4\n\n  - HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)\n  - HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)\n\nChanges in 14.18.0:\n\n  * buffer:\n\n    + introduce Blob\n    + add base64url encoding option\n\n  * child_process:\n\n    + allow options.cwd receive a URL\n    + add timeout to spawn and fork\n    + allow promisified exec to be cancel\n    + add 'overlapped' stdio flag\n\n  * dns: add 'tries' option to Resolve options\n  * fs:\n\n    + allow empty string for temp directory prefix\n    + allow no-params fsPromises fileHandle read\n    + add support for async iterators to fsPromises.writeFile\n\n  * http2: add support for sensitive headers\n  * process: add 'worker' event\n  * tls: allow reading data into a static buffer\n  * worker: add setEnvironmentData/getEnvironmentData\n\nChanges in 14.17.6\n\n  * deps: upgrade npm to 6.14.15 which fixes a number of\n    security issues\n    (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712,\n     bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134,\n     bsc#1190053, CVE-2021-39135)\n\nThis update was imported from the SUSE:SLE-15-SP2:Update update project.","status":"published","published":"2021-12-10T09:43:16Z","modified":"2026-02-04T03:51:21.183743Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2021:1574-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).\n- CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).\n- CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057). \n- CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056). \n- CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055). \n- CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054). \n- CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053). \n\nThis update was imported from the SUSE:SLE-15-SP2:Update update project.","status":"published","published":"2021-12-12T01:19:11Z","modified":"2026-02-04T04:22:32.376783Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2021:3940-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).\n- CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).\n- CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057). \n- CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056). \n- CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055). \n- CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054). \n- CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053). \n","status":"published","published":"2021-12-06T13:43:51Z","modified":"2025-05-07T18:12:32.27718Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2021:3964-1","title":"Security update for nodejs14","description":"This update for nodejs14 fixes the following issues:\n\nnodejs14 was updated to 14.18.1:\n\n* deps: update llhttp to 2.1.4\n\n  - HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)\n  - HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)\n\nChanges in 14.18.0:\n\n  * buffer:\n\n    + introduce Blob\n    + add base64url encoding option\n\n  * child_process:\n\n    + allow options.cwd receive a URL\n    + add timeout to spawn and fork\n    + allow promisified exec to be cancel\n    + add 'overlapped' stdio flag\n\n  * dns: add 'tries' option to Resolve options\n  * fs:\n\n    + allow empty string for temp directory prefix\n    + allow no-params fsPromises fileHandle read\n    + add support for async iterators to fsPromises.writeFile\n\n  * http2: add support for sensitive headers\n  * process: add 'worker' event\n  * tls: allow reading data into a static buffer\n  * worker: add setEnvironmentData/getEnvironmentData\n\nChanges in 14.17.6\n\n  * deps: upgrade npm to 6.14.15 which fixes a number of\n    security issues\n    (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712,\n     bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134,\n     bsc#1190053, CVE-2021-39135)\n","status":"published","published":"2021-12-07T07:57:43Z","modified":"2025-05-07T18:12:32.336642Z","updated_at":"2026-11-02T16:58:32.266854Z"},{"id":"openSUSE-SU-2024:11616-1","title":"nodejs14-14.18.1-1.1 on GA media","description":"These are all security issues fixed in the nodejs14-14.18.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T02:27:30.535489Z","updated_at":"2026-11-02T16:58:35.195147Z"},{"id":"ROOT-APP-NPM-CVE-2021-37713","title":"CVE-2021-37713 in tar - Patched by Root","description":"Root has patched CVE-2021-37713 in the tar package for Root:npm. Multiple fixed versions available.","status":"published","published":"2026-10-07T08:46:27Z","modified":"2026-10-07T09:15:05.218741678Z","updated_at":"2026-11-02T15:53:27.362922Z"},{"id":"SUSE-SU-2021:3886-1","title":"Security update for nodejs14","description":"This update for nodejs14 fixes the following issues:\n\nnodejs14 was updated to 14.18.1:\n\n* deps: update llhttp to 2.1.4\n\nSecurity fixes:\n\n- HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)\n- HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)\n\nChanges in 14.18.0:\n\n  * buffer:\n\n    + introduce Blob\n    + add base64url encoding option\n\n  * child_process:\n\n    + allow options.cwd receive a URL\n    + add timeout to spawn and fork\n    + allow promisified exec to be cancel\n    + add 'overlapped' stdio flag\n\n  * dns: add 'tries' option to Resolve options\n  * fs:\n\n    + allow empty string for temp directory prefix\n    + allow no-params fsPromises fileHandle read\n    + add support for async iterators to fsPromises.writeFile\n\n  * http2: add support for sensitive headers\n  * process: add 'worker' event\n  * tls: allow reading data into a static buffer\n  * worker: add setEnvironmentData/getEnvironmentData\n\nChanges in 14.17.6:\n\n  * deps: upgrade npm to 6.14.15 which fixes a number of\n    security issues\n    (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712,\n     bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134,\n     bsc#1190053, CVE-2021-39135)\n","status":"published","published":"2021-12-02T12:51:24Z","modified":"2026-02-04T03:34:31.297203Z","updated_at":"2026-11-02T15:53:49.605187Z"},{"id":"SUSE-SU-2021:3940-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers (bsc#1191601).\n- CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).\n- CVE-2021-37701: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190057). \n- CVE-2021-37712: Fixed arbitrary file creation and overwrite in nodejs-tar (bsc#1190056). \n- CVE-2021-37713: Fixed arbitrary code execution and file creation and overwrite in nodejs-tar (bsc#1190055). \n- CVE-2021-39134: Fixed symling following vulnerability in nodejs-arborist (bsc#1190054). \n- CVE-2021-39135: Fixed symling following vulnerability in nodejs-arborist (bsc#1190053). \n","status":"published","published":"2021-12-06T13:43:50Z","modified":"2026-02-04T04:21:55.208732Z","updated_at":"2026-11-02T15:53:50.066806Z"},{"id":"SUSE-SU-2021:3964-1","title":"Security update for nodejs14","description":"This update for nodejs14 fixes the following issues:\n\nnodejs14 was updated to 14.18.1:\n\n* deps: update llhttp to 2.1.4\n\n  - HTTP Request Smuggling due to spaced in headers (bsc#1191601, CVE-2021-22959)\n  - HTTP Request Smuggling when parsing the body (bsc#1191602, CVE-2021-22960)\n\nChanges in 14.18.0:\n\n  * buffer:\n\n    + introduce Blob\n    + add base64url encoding option\n\n  * child_process:\n\n    + allow options.cwd receive a URL\n    + add timeout to spawn and fork\n    + allow promisified exec to be cancel\n    + add 'overlapped' stdio flag\n\n  * dns: add 'tries' option to Resolve options\n  * fs:\n\n    + allow empty string for temp directory prefix\n    + allow no-params fsPromises fileHandle read\n    + add support for async iterators to fsPromises.writeFile\n\n  * http2: add support for sensitive headers\n  * process: add 'worker' event\n  * tls: allow reading data into a static buffer\n  * worker: add setEnvironmentData/getEnvironmentData\n\nChanges in 14.17.6\n\n  * deps: upgrade npm to 6.14.15 which fixes a number of\n    security issues\n    (bsc#1190057, CVE-2021-37701, bsc#1190056, CVE-2021-37712,\n     bsc#1190055, CVE-2021-37713, bsc#1190054, CVE-2021-39134,\n     bsc#1190053, CVE-2021-39135)\n","status":"published","published":"2021-12-07T07:57:42Z","modified":"2026-02-04T04:18:26.314061Z","updated_at":"2026-11-02T15:53:50.066806Z"},{"id":"SUSE-SU-2022:0101-1","title":"Security update for nodejs12","description":"This update for nodejs12 fixes the following issues:\n\n- CVE-2021-44531: Fixed improper handling of URI Subject Alternative Names (bsc#1194511).\n- CVE-2021-44532: Fixed certificate Verification Bypass via String Injection (bsc#1194512).\n- CVE-2021-44533: Fixed incorrect handling of certificate subject and issuer fields (bsc#1194513).\n- CVE-2022-21824: Fixed prototype pollution via console.table properties (bsc#1194514).\n- CVE-2021-22959: Fixed HTTP Request Smuggling due to spaced in headers(bsc#1191601).\n- CVE-2021-22960: Fixed HTTP Request Smuggling when parsing the body (bsc#1191602).\n- CVE-2021-37701: Fixed arbitrary file creation and overwrite vulnerability in nodejs-tar (bsc#1190057).\n- CVE-2021-37712: Fixed arbitrary file creation and overwrite vulnerability in nodejs-tar (bsc#1190056).\n- CVE-2021-37713: Fixed arbitrary file creation/overwrite and arbitrary code execution vulnerability in nodejs-tar (bsc#1190055).\n- CVE-2021-39134: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190054).\n- CVE-2021-39135: Fixed symlink following vulnerability in nodejs-arborist (bsc#1190053).\n","status":"published","published":"2022-01-18T08:35:56Z","modified":"2026-02-04T02:58:44.883212Z","updated_at":"2026-11-02T15:53:50.066806Z"}]}}