# openSUSE-SU-2026:21631-1: Security update for libarchive

> Multiple memory corruption and resource leak flaws in libarchive allow attackers to cause denial of service or potentially execute code via crafted archives.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Aug 2026

## What is openSUSE-SU-2026:21631-1?

openSUSE-SU-2026:21631-1 is a memory corruption vulnerability in libarchive, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

This update for libarchive fixes the following issues:

- Fix creation of temporary files in target directory (bsc#1254340)
- Fix out-of-bounds buffer overrun when using p[H_LEVEL_OFFSET] (bsc#1254341)
- Fix buffer overrun in archive_le32dec when reading truncated 7zip headers (bsc#1254342)
- Fix NULL pointer dereference in archive_acl_from_text_w() (bsc#1260998)
- Fix SEGV in check_7zip_header_in_sfx via ELF offset validation (bsc#1260999)
- Fix out-of-bounds access on ELF 64-bit header (bsc#1261000)
- Fix RAR5 memory leak with many filters (bsc#1261002)
- Fix file descriptor leak in mtree parser cleanup (bsc#1261003)

## Which versions are affected by openSUSE-SU-2026:21631-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libarchive` | openSUSE:Leap 16.0 | All versions | 3.8.1-160000.4.1 |

## How do I fix openSUSE-SU-2026:21631-1?

Apply the vendor's patch.

## Is openSUSE-SU-2026:21631-1 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: openSUSE-SU-2026:21631-1 is a memory corruption vulnerability in libarchive, published on 24 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of openSUSE-SU-2026:21631-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/openSUSE-SU-2026-21631-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-21631-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/openSUSE-SU-2026:21631-1

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