Minimum Versions
The minimum versions ClusterMAX expects on a GPU cluster, and the advisory behind each one.
The minimum accepted version is the oldest version of a component that has no known applicable vulnerability. Running at or above every minimum is the baseline we grade against, not a stretch target.
These are not the newest releases available. They are the lowest versions that are still safe, chosen so an operator pinned to an older branch has a target that does not force a major upgrade.
Every number below is read directly from the same table the ClusterMAX audit uses. Nothing on this page is typed by hand, so the published and graded minimum versions cannot drift apart.
| Component | Minimum safe version | Source |
|---|---|---|
| NVIDIA GPU driverCompare against the minimum version for the driver branch you run, not across branches. | AdvisorySecurity Bulletin: GPU Display Driver - May 2026(May 19, 2026) | |
| NVIDIA Container ToolkitA single minimum version. Anything older is vulnerable to container escape. | 1.19.1 | |
| CUDA ToolkitA single minimum version across all supported CUDA releases. | 13.1 | AdvisorySecurity Bulletin - CUDA Toolkit - January 2026(Jan 20, 2026)CVEs: CVE-2025-33228, CVE-2025-33229, CVE-2025-33230, CVE-2025-33231 |
| ConnectX / BlueField firmwareFirmware is versioned per train. Match the train your adapter ships. |
| |
| BlueField VIRTIO-Net controllerOne minimum version per release line, including the long-term support lines. |
| AdvisorySecurity Bulletin: NVIDIA Networking Bluefield, ConnectX - July 2026(Jul 28, 2026)CVEs: CVE-2026-65094 |
| runcOne minimum version per minor line, so a cluster pinned to an older line still has a target. |
| |
| Docker EngineA single minimum version, read from the Docker Engine release notes. | 29.7.0 | |
| AMD Instinct ROCmOne minimum version per Instinct program. Compare against the minimum version for the accelerator you run, not across programs. | AdvisoryAMD security bulletin(May 12, 2026)CVEs: CVE-2025-21940, CVE-2025-66660, CVE-2025-66664, CVE-2026-0428 | |
| DCGMA single minimum version. | 4.5.3 | |
| DCGM exporterA single minimum version. Tracked separately from DCGM itself. | 4.8.2 | |
| Ubuntu 24.04 packagesPer-CVE package minimum versions. Each one names the Ubuntu security notice that fixed it. |
|
Reading the minimum versions
- •Compare like with like. Where a component ships several supported lines, such as GPU driver branches, firmware trains, or runc minor lines, only the minimum version for your line applies.
- •A version above the minimum for a different line is not a pass. An R570 driver is not covered by the R580 minimum.
- •A minimum version moves only upward. If a version cleared the audit last month and the minimum has since risen, the cluster now needs the newer build.
How the table is maintained
Table generated Aug 27, 2026. A scheduled job checks the upstream feeds every day and rewrites the table when a new bulletin lands, so the minimum versions advance as vendors publish fixes.
The feeds we read are the NVIDIA product security advisories, the AMD security bulletins, the OSV database, Ubuntu security notices, and the Docker Engine release notes. Each row records which one produced its value.
The table is considered stale after 10 days without a refresh, and the audit treats that as a failure of our own tooling rather than a pass for the cluster.
A new bulletin does not fail a cluster the day it appears. Operators get a 3 day grace period to roll the fix out before the new minimum version is enforced.
Machine-readable table
The full table, including per-CVE detail and fix-availability evidence that the page does not render, is served as JSON at /minimum-versions.json. It is the same file the audit reads, published byte for byte.
If you are building anything against these minimum versions, read that endpoint rather than parsing this page. The page layout may change, the JSON schema is versioned.
View the raw JSONThese minimum versions are part of the security criterion every provider is scored against.