Affects ubuntu-pro-client preinstalled on Ubuntu Server and Ubuntu Pro cloud images; allows attacker-controlled APT injection and root RCE, impacting many cloud/enterprise servers.
CVE-2026-11386
Ubuntu Pro client allows APT source injection leading to root code execution.
Is CVE-2026-11386 being exploited?
Not confirmed. CVE-2026-11386 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-11386?
CVE-2026-11386 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-11386?
Not known from our data. No patch reference has been recorded for CVE-2026-11386, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-11386 affect?
CVE-2026-11386 affects ubuntu-pro-client (ubuntu-advantage-tools), Ubuntu Server supported releases, Ubuntu Pro cloud images (auto-attached). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11386?
Restrict/verify contract server, disable ubuntu-pro-client, audit apt sources; apply vendor patch ASAP.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Tampered contract responses can inject APT lines and force apt-get to install malicious packages, achieving root remote code execution.
Immediate action required
- affected< 37.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.