Linux ·
Rocky Linux · Security advisory · January 5, 2026
Rocky Linux · Security advisory · January 5, 2026RLSA-2026:0002: tar security update
RLSA-2026:0002, released January 5, 2026, fixes 1 CVE in tar (version 2:1.35-9.el10_1). None of them is reported as exploited. Patch Radar priority: Routine.
Routine
CVEs closed
1
None rated Critical
Exploited
0
None reported
Highest CVSS
5.6
Base score, 0 to 10
Highest EPSS
0.0049
42nd percentile
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| tar | rocky 10 | 2:1.35-9.el10_1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Routine | CVE-2025-45582 | GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in wh | 5.6 | 0.0049 | None reported |
Showing 1 to 1 of 1
1
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.