dbcve.org
Livepatch ClientApplication · Canonical

CVE-2026-6369

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-20
Fix available
A fix is available. Upgrade to 10.15.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper access control vulnerability in the canonical-livepatch snap client prior to version 10.15.0 allows a local unprivileged user to obtain a sensitive, root-level authentication token by sending an unauthenticated request to the livepatchd.sock Unix domain socket. This vulnerability is exploitable on systems where an administrator has already enabled the Livepatch client with a valid Ubuntu Pro subscription. This token allows an attacker to access Livepatch services using the victim's credentials, as well as potentially cause issues to the Livepatch server.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The canonical-livepatch snap client before version 10.15.0 has improper access control on the livepatchd.sock Unix domain socket. A local unprivileged user can send unauthenticated requests to this socket and obtain a root-level authentication token that was meant for the administrator who enabled Livepatch with a valid Ubuntu Pro subscription. This token allows the attacker to impersonate the victim and access Livepatch services.

MitigationUpgrade the canonical-livepatch snap client to version 10.15.0 or later using 'snap refresh canonical-livepatch'. No configuration changes required; the fix addresses the socket access control vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Livepatch ClientApplication
Affected:< 10.15.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify canonical-livepatch snap is installed
    Run 'snap list canonical-livepatch' to see if the package is installed on the system
    Affected if The snap is not installed - no vulnerability present in that case
  2. Check installed version of canonical-livepatch
    Examine the version number output from 'snap list canonical-livepatch' and compare it to 10.15.0
    Affected if Installed version is less than 10.15.0 - the system is running a vulnerable version
  3. Locate the livepatchd.sock Unix domain socket
    Find the socket file, typically under /snap/canonical-livepatch/current/ or via 'find /snap -name livepatchd.sock 2>/dev/null'
    Affected if The socket exists on the system, indicating the Livepatch service is active
  4. Examine socket file permissions and ownership
    Run 'ls -la' on the livepatchd.sock file to check permissions - the socket should not be world-writable or accessible by unprivileged users
    Affected if Socket permissions allow access by non-root or non-prohibited users, meaning the access control vulnerability is present
  5. Verify the Livepatch service is enabled and running
    Check service status via 'systemctl status snap.canonical-livepatch.service' or 'snap services canonical-livepatch'
    Affected if The service is active and the version is below 10.15.0, the system is vulnerable to the described attack

The system is affected if the canonical-livepatch snap is installed with a version lower than 10.15.0 and the livepatchd.sock socket exists with permissive access controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.15.0 or later
Fixed in 10.15.0
Interim mitigation

Upgrade the canonical-livepatch snap client to version 10.15.0 or later using 'snap refresh canonical-livepatch'. No configuration changes required; the fix addresses the socket access control vulnerability.

Recommended fix High confidence

10.15.0 or later

  1. Check the current installed version of the Livepatch client: snap list canonical-livepatch
  2. Upgrade the Livepatch snap to the latest version: snap refresh canonical-livepatch
  3. Verify the installed version is 10.15.0 or later: snap list canonical-livepatch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Livepatch Client Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6369 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6369 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data