CVE-2026-11386

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-16. A secondary CVSS source baseline 9.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-44911 (ENISA EUVD) · GHSA-9836-vm3x-qwmj (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An input validation and injection vulnerability exists in Canonical ubuntu-pro-client (formerly ubuntu-advantage-tools). The client constructs APT source files (such as /etc/apt/sources.list.d/ubuntu-.list or their DEB822 equivalents) using data received directly from the contract server response via the directives.suites[] and directives.aptURL fields. Because the client utilizes Python's str.format() to write these files without performing escaping, validation, or newline character filtering, a malicious or tampered contract response containing embedded newline (\n) characters can successfully inject arbitrary, attacker-controlled deb configuration lines into root-owned APT sources. When combined with the unvalidated additionalPackages[] field—which is passed positionally into a root-executed apt-get install command—an attacker capable of spoofing or manipulating the contract response (e.g., via a compromised internal infrastructure, an intercepted connection utilizing a trusted CA, or local logical bugs) can force the client to fetch and install malicious packages. This ultimately leads to arbitrary code execution with root privileges on the affected system. This component is preinstalled on supported Ubuntu Server releases and auto-attaches by default on cloud provider Ubuntu Pro images.

CVSS v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 16, 2026

Last Modified

July 16, 2026

References (1)

Vendor Advisories for CVE-2026-11386(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuubuntu-pro-client-l10n (37.2ubuntu0.1) @ resolute2026-10-29ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 26× in last 7d / 83× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 639 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 539 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-29 12:33 UTCEG score recompute
  3. 2026-10-29 12:33 UTCVendor advisory
  4. 2026-10-29 12:33 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-10-28 11:19 UTCEG score recompute
  7. 2026-10-28 11:19 UTCVendor advisory
  8. 2026-10-28 11:19 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-10-27 09:40 UTCEG score recompute
  11. 2026-10-27 09:40 UTCVendor advisory
  12. 2026-10-27 09:40 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  13. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-26 08:32 UTCEG score recompute
  15. 2026-10-26 08:32 UTCVendor advisory
  16. 2026-10-26 08:32 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  17. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-25 14:51 UTCEG score recompute
  19. 2026-10-25 07:22 UTCEG score recompute
  20. 2026-10-25 07:22 UTCVendor advisory
  21. 2026-10-25 07:22 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  22. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-24 06:12 UTCEG score recompute
  24. 2026-10-24 06:12 UTCVendor advisory
  25. 2026-10-24 06:12 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
Show 75 more
  1. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-23 05:03 UTCEG score recompute
  3. 2026-10-23 05:03 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  4. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-22 03:53 UTCEG score recompute
  6. 2026-10-22 03:53 UTCVendor advisory
  7. 2026-10-22 03:52 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  8. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-21 02:43 UTCEG score recompute
  10. 2026-10-21 02:43 UTCVendor advisory
  11. 2026-10-21 02:43 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  12. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-20 01:34 UTCEG score recompute
  14. 2026-10-20 01:34 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  15. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-19 00:25 UTCEG score recompute
  17. 2026-10-19 00:24 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-18 05:05 UTCEG score recompute
  20. 2026-10-17 23:14 UTCEG score recompute
  21. 2026-10-17 23:14 UTCVendor advisory
  22. 2026-10-17 23:14 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-16 22:05 UTCEG score recompute
  25. 2026-10-16 22:05 UTCVendor advisory
  26. 2026-10-16 22:05 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  27. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  28. 2026-10-15 18:35 UTCEG score recompute
  29. 2026-10-15 18:34 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  30. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-10-14 12:16 UTCEG score recompute
  33. 2026-10-14 12:15 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  34. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-10-13 11:04 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  36. 2026-10-12 16:37 UTCEG score recompute
  37. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-10-12 09:51 UTCVendor advisory
  39. 2026-10-12 09:51 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  40. 2026-10-11 20:13 UTCEG score recompute
  41. 2026-10-11 18:25 UTCEG score recompute
  42. 2026-10-11 14:59 UTCEG score recompute
  43. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  45. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  46. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  47. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  49. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  50. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  51. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  52. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  53. 2026-10-01 15:10 UTCVendor advisory
  54. 2026-10-01 15:10 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  55. 2026-10-01 11:24 UTCEG score recompute
  56. 2026-10-01 11:24 UTCVendor advisory
  57. 2026-10-01 11:24 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  58. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  59. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  60. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  61. 2026-09-28 13:14 UTCVendor advisory
  62. 2026-09-28 13:14 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  63. 2026-09-28 08:37 UTCEG score recompute
  64. 2026-09-28 08:37 UTCVendor advisory
  65. 2026-09-28 08:37 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  66. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  67. 2026-09-24 13:17 UTCVendor advisory
  68. 2026-09-24 13:17 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  69. 2026-09-24 08:32 UTCEG score recompute
  70. 2026-09-24 08:32 UTCVendor advisory
  71. 2026-09-24 08:32 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  72. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  73. 2026-09-23 10:59 UTCVendor advisory
  74. 2026-09-23 10:59 UTCGHSA enrichmentGHSA-9836-vm3x-qwmj · GitHub severity CRITICAL · GitHub CVSS 9.0
  75. 2026-09-23 06:50 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Same vendor

2 shown

ubuntu:USN-8555-1

Frequently asked(5)

What is CVE-2026-11386?
CVE-2026-11386 is a critical-severity vulnerability; its CVE record was published on July 16, 2026. An input validation and injection vulnerability exists in Canonical ubuntu-pro-client (formerly ubuntu-advantage-tools). The client constructs APT source files (such as /etc/apt/sources.list.d/ubuntu-.list or their DEB822 equivalents) using data received directly from the contract server response…
When was CVE-2026-11386 made public?
CVE-2026-11386 was made public on July 16, 2026: that is the date its CVE record's CNA, Canonical Ltd., gives for when the vulnerability was made public. The CVE record itself was published on July 16, 2026. EchelonGraph's copy of the record carries a last-modified date of July 16, 2026; the record at its source may have been updated since.
Is CVE-2026-11386 actively exploited?
CVE-2026-11386 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-11386?
CVE-2026-11386 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-11386?
A fix for CVE-2026-11386 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-11386 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11386

Explore →

Is Your Infrastructure Affected by CVE-2026-11386?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs