Vulnerability in containerd-app (UBUNTU-CVE-2026-53489)

Summary

Vulnerability in containerd-app (UBUNTU-CVE-2026-53489). Confidential information can be exposed externally. Mitigation: upgrade to 2.2.1-0ubuntu1~22.04.2 or later.

Original description

The description as published by the source.

containerd is an open-source container runtime. Versions prior to 2.3.2, 2.2.5 and 2.1.9 contain a bug where the CRI plugin restores container.log from a checkpoint image without validating a symlinked path. This could result in reading an arbitrary file on the host via kubectl logs. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.

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-53489 has been found in containerd-app.
Confidential information can be exposed externally.
What to do: upgrade containerd-app to 2.2.1-0ubuntu1~22.04.2 or later.
If unsure, ask your IT team or search "containerd-app UBUNTU-CVE-2026-53489" on the vendor's site.

UBUNTU-CVE-2026-53489 (containerd-app)
Attack vector: local / no user interaction
Patched: 2.2.1-0ubuntu1~22.04.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 containerd-app.

📍 Affected scope

Check the vendor advisory for the affected versions of containerd-app.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

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

Affected packages

Ubuntu:22.04:LTS containerd-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.1-0ubuntu1~22.04.2"}]}]

Ubuntu:24.04:LTS containerd-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.1-0ubuntu1~24.04.3"}]}]

Ubuntu:25.10 containerd-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.1-0ubuntu1~25.10.2"}]}]

Ubuntu:25.10 containerd-stable

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.6-0ubuntu1~25.10.2"}]}]

Ubuntu:26.04:LTS containerd-app

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2-0ubuntu1.1"}]}]

Ubuntu:26.04:LTS containerd-stable

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.2-0ubuntu1.1"}]}]

References

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