# SUSE-SU-2026:3587-1: Security update for libarchive

> A security update for libarchive addresses memory corruption, file descriptor leaks, and null dereferences that could allow denial of service or code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Aug 2026

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

SUSE-SU-2026:3587-1 is a memory corruption vulnerability in libarchive, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for libarchive fixes the following issues:

- creating temporary files in the current working directory instead of the target directory can lead to file creation
  failures when the working directory is not writable (bsc#1254340).
- file descriptor leak in the mtree parser cleanup path could lead to file descriptor exhaustion and denial of service
  (bsc#1261003).
- NULL pointer dereference in archive_acl_from_text_w() could lead to a segmentation fault (bsc#1260998).
- reading from an invalid index when buffer size is smaller than H_LEVEL_OFFSET can lead to an out-of-bounds buffer
  overrun (bsc#1254341).

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libarchive` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.3.3-32.20.1 |

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

Apply the vendor's patch.

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

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

## Fix prompt for AI coding agents

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

What it is: SUSE-SU-2026:3587-1 is a memory corruption vulnerability in libarchive, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:3587-1 in the wild and no public exploit code.

Affected product: libarchive. 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-3587-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-3587-1/index.md)
```

## Sources

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

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