Skip to main content
Version: 0.4 · current

Track updates and advisories

How-to guideReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Super admin, Entity admin, Installer (Linux administrator)
PlansFree · Pro · EnterpriseDeploymentSelf-hosted

The updates module compares what is installed on each resource with what the vendors have released. It shows how far each system is behind, when its support ends and which security advisories concern it. It is information only: Excubius never installs anything, and the decision and the change stay with you. This guide shows how to turn the module on, read the page, get alerts and keep its sources current.

Before you begin​

  • The feature monitoring.updates is on in Settings › Instance. A super admin switches it.
  • The checks that turn the feeds into alerts run on a resource of type Monitoring platform itself. If you do not have one, an entity admin adds it with Resources › Add resource.
  • SQL Server instances report their build once their checks run, or once you run Discover on them.
  • The server reaches the public feeds over HTTPS: dataplat.github.io or raw.githubusercontent.com, endoflife.date and api.msrc.microsoft.com. Without that, see Run without internet access.

Read the page​

Open Updates & advisories. The figures at the top count the resources behind the latest build, missing security fixes, with pending security updates, waiting for a reboot, near or past the end of support, and the advisories of the last 14 days. Everything follows the entity chosen in the picker.

Per resource​

The Per resource tab compares, for each resource, what is installed with what is available:

ResourceInstalledCompared with
SQL Server instanceThe build it reports, or the build that discovery recordedThe newest build of its servicing line. An instance on the security-only (GDR) line is compared with the latest GDR; one on the cumulative update line with the latest cumulative update. The newest build of the major version is shown too
Windows hostIts caption and versionIts Windows Server release cycle
Linux hostIts distribution and versionIts distribution's release cycle

For SQL Server, How far behind gives the number of newer builds on the line, how many are cumulative updates and how long ago the first missing one came out. Each build links to its KB article. Use Only those behind to keep only what needs attention.

Pending updates come from whatever reports them: the Windows Update Agent in search mode, a check-only dnf or apt run, Azure Update Manager, NinjaOne, or a pending_updates attribute on the resource. The highest count reported wins, and a pending reboot from any of them is shown.

End of support​

The End of support tab shows each product cycle in use on a timeline, the soonest end first, with the resources on it: mainstream support, security fixes only, and paid extended updates.

StatusMeaning
SupportedMainstream support
Security fixes onlyPast mainstream support; security fixes are still released
Extended security updatesPast the end of security support; paid extended updates are available until a later date
End of supportNo more fixes

Advisories​

The Advisories tab lists Microsoft security advisories for SQL Server and Windows Server, newest first, each with its CVE, impact, maximum severity, CVSS score, whether it is exploited or publicly disclosed, its KB articles and the fixed builds.

  • Published is Last 14 days by default: what came out since the last patch Tuesday or two.
  • Only those that concern our resources is on by default.
  • Filter by Severity, Product or text with Search.

For a SQL Server instance, an advisory is missing when the instance is below the fixed build of its own servicing line, fixed when it is at or above it, and unknown when the advisory gives no fixed build for that version. For a Windows host, an advisory of its Windows Server version applies: the version alone does not say which monthly update is installed, so use the pending-updates checks for that.

How severity is decided​

SituationSeverity
End of support has passed, or is less than 30 days awayCritical
End of support is less than 180 days awayWarning
An advisory's fix is missing on the instanceWarning
Security updates are pendingWarning
SQL Server is behind by more than 90 daysWarning
SQL Server is behind, more recentlyInfo

An advisory takes Microsoft's maximum severity: Critical is critical, Important is warning, Moderate and Low are info. An advisory exploited in the wild is always critical.

Get alerts​

The checks of the updates module raise alerts of category Advisories. Find them in the Alert inbox with the Category filter; they follow the same Slack routing as any other alert.

CheckRaises
updates.sqlserver_latest_buildAn event when a new build of a SQL Server version in use is released
updates.endoflifeThe days left before the end of support of each cycle in use: warning under 180 days, critical under 30
updates.msrc_securityAn event when Microsoft publishes a new monthly release for a product in use
updates.azure_update_managerSecurity and critical updates pending on an Azure virtual machine
updates.ninjaone_patchesPending patches reported by NinjaOne

Keep the feeds current​

The feeds are read by the server on a schedule, not by the collector, and kept in the database. Requests are plain HTTPS GETs that ask only for what changed, so an unchanged feed costs little.

FeedSourceRefreshed
SQL Server buildsThe dbatools build reference: every RTM, service pack, cumulative update and GDR build of SQL Server 2016 to 2025, with its KB article and release date. MIT LicenseEvery 12 hours
Product support datesThe endoflife.date API. MIT LicenseEvery 24 hours
Microsoft security advisoriesThe Microsoft Security Response Center CVRF API: the monthly releases of the last three monthsEvery 6 hours

The Sources panel of the page shows each feed's state: Up to date, Last read failed; using the previous copy, Not reachable; using the copy shipped with the release, or Not read yet. A super admin can read every feed at once with Refresh now.

When a feed cannot be reached, the last good copy is kept and the next attempt comes sooner: after 15 minutes, doubling up to the feed's normal interval.

Run without internet access​

An installation that never reaches a feed uses the copies shipped with the release for SQL Server builds and support dates, as of the release date. Microsoft advisories have no shipped copy.

Change the behaviour with these settings in the server's configuration file, then restart the platform:

SettingDefaultMeaning
EXCUBIUS_FEEDS_ENABLEDtruefalse never reads a feed; the shipped copies are used. For air-gapped servers
EXCUBIUS_FEED_SQLSERVER_BUILDS_URLSThe dbatools site, then GitHubAddresses separated by spaces, tried in order. Put an internal mirror first
EXCUBIUS_FEED_ENDOFLIFE_URLhttps://endoflife.date/apiBase address
EXCUBIUS_FEED_MSRC_URLhttps://api.msrc.microsoft.com/cvrf/v3.0Base address
EXCUBIUS_FEED_MSRC_MONTHS3Monthly releases kept up to date
EXCUBIUS_FEED_TIMEOUT_SECONDS60Per request

Feed requests go through HTTPS_PROXY when it is set.