Vulnerability in Cockpit (CVE-2026-91142)
Summary
Vulnerability in Cockpit (CVE-2026-91142). Risk of unauthorized operations or information disclosure. Exploitable via lastlog.
Original description
The description as published by the source.
A flaw was found in Cockpit. An integer overflow vulnerability in the do_lastlog() function, specifically in the offset calculation for lastlog entries on ILP32 (Integer, Long, Pointer 32-bit) builds, can be exploited. A low-privileged authenticated user with a specially provisioned large User ID (UID) can cause the computed offset to wrap around. This allows the user to perform unauthorized reads and writes to other users' lastlog records, potentially disclosing or altering sensitive login accounting information.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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 CVE-2026-91142 has been found in Cockpit.
Attackers can target a specific entry point like lastlog over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Cockpit CVE-2026-91142" on the vendor's site.
CVE-2026-91142 (Cockpit) — CWE-190 / CVSS v3 3.6
Attack vector: local / no user interaction
Attack surface: lastlog
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.
A vulnerability (CWE-190) exists in Cockpit. Attackers reach the vulnerable code path via lastlog.
Check the vendor advisory for the affected versions of Cockpit. Attack surface: lastlog.
Severity: Low (CVSS 3.6/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Cockpit' . 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
-
1Identify exposure identify
grep -r 'Cockpit' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Cockpitを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web access.redhat.com
- web bugzilla.redhat.com
- web nvd.nist.gov
- web github.com