# SUSE-SU-2026:24200-1: Security update for ntfs-3g_ntfsprogs


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 8 Oct 2026

## What is SUSE-SU-2026:24200-1?

SUSE-SU-2026:24200-1 is a vulnerability in ntfs-3g_ntfsprogs, published on 8 Oct 2026. 

### Official description

This update for ntfs-3g_ntfsprogs fixes the following issues:

- Denial-of-service in ntfs_inode_attach_all_extents() (bsc#1281758).
- Heap buffer overflow in ntfs_acl_owner() (bsc#1281756).
- Heap buffer overflow in ntfs_check_restart_area() (bsc#1281759).
- Heap buffer overflow in ntfs_ea_check_wsldev() (bsc#1281760).
- Heap buffer overflow in ntfs_external_attr_find() (bsc#1281761).
- Heap buffer overflow in ntfs_same_sid() (bsc#1281757).
- Heap data corruption in ntfs_mapping_pairs_decompress_i() (bsc#1281762).
- Heap out of bounds read/write in ntfs_ie_add_vcn() (bsc#1281763).

## Which versions are affected by SUSE-SU-2026:24200-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Server 16.0 | All versions | 2022.10.3-160000.5.1 |
| `ntfs-3g_ntfsprogs` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2022.10.3-160000.5.1 |

## How do I fix SUSE-SU-2026:24200-1?

Upgrade to a fixed version.

## Is SUSE-SU-2026:24200-1 being exploited?

There is no known exploitation of SUSE-SU-2026:24200-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2026:24200-1 and fix it if it is affected.

What it is: SUSE-SU-2026:24200-1 is a vulnerability in ntfs-3g_ntfsprogs, published on 8 Oct 2026. 
Exploitation: There is no known exploitation of SUSE-SU-2026:24200-1 in the wild and no public exploit code.

Affected product: ntfs-3g_ntfsprogs. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/SUSE-SU-2026-24200-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-24200-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:24200-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2026-24200-1/
Summaries are generated and may contain mistakes; the official description above is the record.