Track updates and advisories
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.updatesis 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.ioorraw.githubusercontent.com,endoflife.dateandapi.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:
| Resource | Installed | Compared with |
|---|---|---|
| SQL Server instance | The build it reports, or the build that discovery recorded | The 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 host | Its caption and version | Its Windows Server release cycle |
| Linux host | Its distribution and version | Its 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.
| Status | Meaning |
|---|---|
| Supported | Mainstream support |
| Security fixes only | Past mainstream support; security fixes are still released |
| Extended security updates | Past the end of security support; paid extended updates are available until a later date |
| End of support | No 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
| Situation | Severity |
|---|---|
| End of support has passed, or is less than 30 days away | Critical |
| End of support is less than 180 days away | Warning |
| An advisory's fix is missing on the instance | Warning |
| Security updates are pending | Warning |
| SQL Server is behind by more than 90 days | Warning |
| SQL Server is behind, more recently | Info |
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.
| Check | Raises |
|---|---|
updates.sqlserver_latest_build | An event when a new build of a SQL Server version in use is released |
updates.endoflife | The days left before the end of support of each cycle in use: warning under 180 days, critical under 30 |
updates.msrc_security | An event when Microsoft publishes a new monthly release for a product in use |
updates.azure_update_manager | Security and critical updates pending on an Azure virtual machine |
updates.ninjaone_patches | Pending 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.
| Feed | Source | Refreshed |
|---|---|---|
| SQL Server builds | The 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 License | Every 12 hours |
| Product support dates | The endoflife.date API. MIT License | Every 24 hours |
| Microsoft security advisories | The Microsoft Security Response Center CVRF API: the monthly releases of the last three months | Every 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:
| Setting | Default | Meaning |
|---|---|---|
EXCUBIUS_FEEDS_ENABLED | true | false never reads a feed; the shipped copies are used. For air-gapped servers |
EXCUBIUS_FEED_SQLSERVER_BUILDS_URLS | The dbatools site, then GitHub | Addresses separated by spaces, tried in order. Put an internal mirror first |
EXCUBIUS_FEED_ENDOFLIFE_URL | https://endoflife.date/api | Base address |
EXCUBIUS_FEED_MSRC_URL | https://api.msrc.microsoft.com/cvrf/v3.0 | Base address |
EXCUBIUS_FEED_MSRC_MONTHS | 3 | Monthly releases kept up to date |
EXCUBIUS_FEED_TIMEOUT_SECONDS | 60 | Per request |
Feed requests go through HTTPS_PROXY when it is set.