← Back
UBUNTU-CVE-2026-41254
Vulnerability in lcms2 (UBUNTU-CVE-2026-41254)
Summary
vulnerability in lcms2 (UBUNTU-CVE-2026-41254). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.12~rc1-2ubuntu0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2026-41254** has been found in lcms2.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade lcms2 to **2.12~rc1-2ubuntu0.1** or later.
If unsure, ask your IT team or search "lcms2 UBUNTU-CVE-2026-41254" on the vendor's site.
UBUNTU-CVE-2026-41254 (lcms2) —
Attack vector: local / unauthenticated / no user interaction
Patched: `2.12~rc1-2ubuntu0.1` — 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 lcms2.
📍 Affected scope
lcms2 — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.12~rc1-2ubuntu0.1**.
🛡️ 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 'lcms2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'lcms2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `lcms2` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade lcms2 to 2.12~rc1-2ubuntu0.1ステージング環境で 2.12~rc1-2ubuntu0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:14.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:16.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:18.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:20.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:22.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.12~rc1-2ubuntu0.1"}]}]
Ubuntu:24.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.14-2ubuntu0.1"}]}]
Ubuntu:25.10
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.16-2ubuntu0.1"}]}]
Ubuntu:26.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.17-1ubuntu0.1"}]}]
Ubuntu:Pro:14.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.5-0ubuntu4.2+esm1"}]}]
Ubuntu:Pro:16.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.6-3ubuntu2.1+esm1"}]}]
Ubuntu:Pro:18.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9-1ubuntu0.1+esm1"}]}]
Ubuntu:Pro:20.04:LTS
lcms2
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9-4ubuntu0.1~esm1"}]}]
References
- advisory https://ubuntu.com/security/notices/USN-8209-1
- advisory https://ubuntu.com/security/notices/USN-8209-2
- report https://ubuntu.com/security/CVE-2026-41254
- report https://www.cve.org/CVERecord?id=CVE-2026-41254
- report https://www.openwall.com/lists/oss-security/2026/04/17/16
- report https://abhinavagarwal07.github.io/posts/lcms2-cubesize-overflow/