Vulnerability in libarchive (UBUNTU-CVE-2026-15028)

Summary

Vulnerability in libarchive (UBUNTU-CVE-2026-15028). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.8.5-1ubuntu2.2 or later.

Original description

The description as published by the source.

A flaw was found in libarchive. This vulnerability allows a remote attacker to trigger a heap overflow by providing a specially crafted tar archive. The issue occurs during the parsing of a PAX extended header containing a malformed SUN.holesdata sparse-file attribute. Successful exploitation could lead to a denial of service, making the system unavailable, or potentially allow for arbitrary code execution, giving the attacker control over the affected system.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-15028 has been found in libarchive.
Risk of unauthorized operations or information disclosure.
What to do: upgrade libarchive to 3.8.5-1ubuntu2.2 or later.
If unsure, ask your IT team or search "libarchive UBUNTU-CVE-2026-15028" on the vendor's site.

UBUNTU-CVE-2026-15028 (libarchive)
Attack vector: local
Patched: 3.8.5-1ubuntu2.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in libarchive.

📍 Affected scope

Check the vendor advisory for the affected versions of libarchive.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.8.5-1ubuntu2.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'libarchive' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'libarchive' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で libarchive を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade libarchive to 3.8.5-1ubuntu2.2
```
ステージング環境で 3.8.5-1ubuntu2.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:26.04:LTS libarchive

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.8.5-1ubuntu2.2"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org
report access.redhat.com
report github.com