Linux · 
openSUSE Leap · Security advisory · July 30, 2026
openSUSE Leap · Security advisory · July 30, 2026OPENSUSE-SU-2026:21484-1: ntfs-3g_ntfsprogs security update
OPENSUSE-SU-2026:21484-1, released July 30, 2026, fixes 9 CVEs in ntfs-3g_ntfsprogs (version 2022.10.3-160000.4.1). None of them is reported as exploited. Patch Radar priority: High.
High
CVEs closed
9
None rated Critical
Exploited
0
None reported
Highest CVSS
8.1
Base score, 0 to 10
Highest EPSS
0.0017
5th percentile
Priority of the 9 CVEs
Patch now 0
Urgent 0
High 8
Routine 1
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| ntfs-3g_ntfsprogs | opensuse-leap 16.0 | 2022.10.3-160000.4.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| High | CVE-2026-42616 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in cat() in ntfscat.c that allows an attacker to corrupt heap memory in the ntfscat binary by crafting a malicious NTFS image. The overflow is triggered by reading a file. | 7.8 | 0.0017 | None reported |
| High | CVE-2026-46569 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_ib_copy_tail(), in libntfs-3g/index.c, that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by extending a directory, e.g., by creating a file. | 7.7 | 0.0016 | None reported |
| High | CVE-2026-46570 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_index_walk_down() in libntfs-3g/index.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by reading the special crafted file metadata. | 8.1 | 0.0015 | None reported |
| High | CVE-2026-46572 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_ib_cut_tail() in libntfs-3g/index.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by creating a file in a specially crafted directory. | 7.4 | 0.0015 | None reported |
| High | CVE-2026-42617 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_ir_to_ib() in index.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by extending a directory, e.g., by creating a file. | 7.1 | 0.0015 | None reported |
| High | CVE-2026-42618 | In NTFS-3G before 2026.7.7, a heap buffer overflow exists in ntfs_decompress() in compress.c that allows an attacker to corrupt one byte of heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by reading the special crafted file. | 7.1 | 0.0015 | None reported |
| High | CVE-2026-56135 | In NTFS-3G through 2026.2.25, a heap-based buffer overflow exists in the function build_inherited_id() in libntfs-3g/security.c that allows an attacker to corrupt heap memory in the SUID-root ntfs-3g binary by crafting a malicious NTFS image. The overflow is triggered by creating a file in a crafted directory. | 7.4 | 0.0014 | None reported |
| High | CVE-2026-56136 | In NTFS-3G through 2026.2.25, an out-of-bounds read exists in ntfs_ir_nill() in libntfs-3g/index.c that allows an attacker to read possibly confidential information in an ntfs-3g process by crafting a malicious NTFS image. This read operation is triggered by creation of a file with a crafted name. | 7.1 | 0.0012 | None reported |
| Routine | CVE-2026-46571 | In NTFS-3G before 2026.7.7, a out-of-bounds read exists in ntfs_fix_file_name() in libntfs-3g/reparse.c that allows an attacker to read possibly confidential information in ntfs-3g process memory by crafting a malicious NTFS image. The out-of-bounds read is triggered by a readlink on a corrupted file. | 5.5 | 0.0013 | None reported |
Showing 1 to 9 of 9
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.