A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.
CVE-2026-18477
Score 4.4 from GitHub Security Advisory published 2026-08-03. a secondary CVSS source baseline 4.4; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.4
- EG Score
- 4.4(high)
- EG Risk
- 20(Track)EG Risk 20/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
August 3, 2026
Last Modified
August 13, 2026
Advisory Details (2)
Auto-updated Aug 3, 2026CVE-2026-18477 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-18477Vendor Advisories for CVE-2026-18477(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-18477Microsoft Security Response Center (MSRC)Medium
Tar: tar: toctou in incremental dumpdir 'x' rename handling allows restore path escape
- GHSA-v7fx-gjvh-347cGitHub Security AdvisoriesMedium
A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename...
- RHSA-2026:49361Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | tar-main-1.35-9.1.hum1 | 2026-08-01 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | 1.34+dfsg-1 ... 1.35+dfsg-4 (11 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | 1.34+dfsg-1.2 ... 1.35+dfsg-4 (9 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | 1.35+dfsg-3.1, 1.35+dfsg-4 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| tar | 1.35+dfsg-3.1, 1.35+dfsg-4 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 25× in last 7d / 65× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 02:14 UTCEG score recompute
- 2026-08-20 02:14 UTCVendor advisory
- 2026-08-20 02:14 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 00:37 UTCEG score recompute
- 2026-08-19 00:37 UTCVendor advisory
- 2026-08-19 00:37 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:01 UTCEG score recompute
- 2026-08-17 23:01 UTCVendor advisory
- 2026-08-17 23:00 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 21:24 UTCEG score recompute
- 2026-08-16 21:24 UTCVendor advisory
- 2026-08-16 21:24 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:48 UTCEG score recompute
- 2026-08-15 19:48 UTCVendor advisory
- 2026-08-15 19:48 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 18:12 UTCEG score recompute
- 2026-08-14 18:12 UTCVendor advisory
- 2026-08-14 18:12 UTCGHSA enrichment
Show 40 moreShow fewer
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 16:36 UTCVendor advisory
- 2026-08-13 16:36 UTCGHSA enrichment
- 2026-08-12 19:52 UTCEG score recompute
- 2026-08-12 19:52 UTCVendor advisory
- 2026-08-12 19:52 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 18:17 UTCEG score recompute
- 2026-08-11 18:17 UTCVendor advisory
- 2026-08-11 18:16 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-10 16:37 UTCVendor advisory
- 2026-08-10 16:37 UTCGHSA enrichment
- 2026-08-09 14:47 UTCEG score recompute
- 2026-08-09 14:47 UTCVendor advisory
- 2026-08-09 14:47 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:12 UTCEG score recompute
- 2026-08-08 13:12 UTCVendor advisory
- 2026-08-08 13:12 UTCGHSA enrichment
- 2026-08-07 11:36 UTCEG score recompute
- 2026-08-07 11:36 UTCVendor advisory
- 2026-08-07 11:36 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 09:59 UTCEG score recompute
- 2026-08-06 09:59 UTCVendor advisory
- 2026-08-06 09:59 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 08:23 UTCEG score recompute
- 2026-08-05 08:23 UTCGHSA enrichment
- 2026-08-05 07:18 UTCEG score recompute
- 2026-08-05 07:17 UTCGHSA enrichment
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 05:38 UTCEG score recompute
- 2026-08-04 05:38 UTCGHSA enrichment
- 2026-08-03 17:40 UTCEG score recompute
- 2026-08-03 17:12 UTCEG score recompute
- 2026-08-03 16:19 UTCEG score recompute
- 2026-08-03 16:18 UTCMITRE cvelistV5first tracked
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-1009EG 10.0EPSS p93HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-1162EG 10.0EPSS p96HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
Frequently asked(5)
What is CVE-2026-18477?
When was CVE-2026-18477 disclosed?
Is CVE-2026-18477 actively exploited?
What is the CVSS score of CVE-2026-18477?
How do I remediate CVE-2026-18477?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18477
Is Your Infrastructure Affected by CVE-2026-18477?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.