Nvidia's 114-CVE driver bulletin went live reading 'Default Summary' for two days
Nvidia published its September 2026 GPU display driver security bulletin with the words "Default Summary" standing where the summary should have been, and it stood that way for two days and six hours. Nvidia's own product-security repository added the document at 17:33 UTC on September 30 and replaced that line at 23:41 UTC on October 2, in commit b6233b6f.

A library illustration of glowing letters falling towards a circular mirror. Nvidia PSIRT publishes its security bulletins only on GitHub from October 1.
Bulletin 5861 is the one that tells GeForce, RTX, vGPU and cloud gaming owners which driver build carries the fixes, which on the desktop covers most of the cards in Steam's September hardware survey. Counting one row per CVE identifier in the bulletin's own vulnerability table gives 114 unique entries, 78 of them rated High and 36 Medium, with no Critical entry and a highest base score of 7.8 that 70 of the 114 share, on a read at 12:36 UTC on October 5.
The replacement text came with its stylesheet attached
What Nvidia dropped in is a plain instruction: "NVIDIA has released a software security update for NVIDIA GPU Display Driver to address the issues that are disclosed in this bulletin." It then sends owners to the NVIDIA Driver Downloads page, and to the Licensing Portal for the vGPU software and cloud gaming builds.
The replacement did not arrive clean. The human-readable Markdown copy now carries a span tag with CSS custom properties inside it, among them var(--psirt-font-family-sans), which resolve to nothing at all outside the stylesheet they came from.
The revision history still says initial release
Nothing inside the bulletin records any of this. Its revision history carries a single row reading "1.0.0 | 2026-09-30 | Initial Release", and its dateline still reads "Updated 2026-09-30", so the version a reader saw on September 30 and the one there now are presented as the same document.
The commit log is the only record of the change. Nvidia tells readers to "Subscribe to this repository to receive notifications on new or revised NVIDIA Security Bulletins" in its repository README, and that subscription is what now stands in for a revision note.
The machine-readable copy was rewritten at the same time, and it carries its own version of the problem. Nvidia’s CSAF file for 5861 had no document-level summary at all before October 2, and the one added then matches the Markdown word for word. Its tracking block still gives version 1.0.0, a current release date of September 30 and a revision history whose only entry is Initial Release, which is what any tool parsing the file automatically will read.
Nvidia set October 1 as the date from which PSIRT would publish security bulletins only on GitHub, in Markdown, CSAF and CVE formats. 5861 landed the day before that, and at 114 CVEs it is an outlier among its neighbours: 14 in the Infrastructure Controller bulletin of September 22, and one each in the two published on September 29.
The bulletins either side of it opened properly
The slip is confined to 5861. Nvidia’s DeepStream bulletin of September 29 opens "NVIDIA has released a software update for NVIDIA® DeepStream", the Networking BlueField and ConnectX bulletin of the same date opens with the same sentence shaped to its own products, and the Infrastructure Controller bulletin names the repository owners should clone from. Whatever produced the placeholder affected one document, not the template.
The practical advice in 5861 has not changed since the fix: find the branch you are on and install the build the bulletin names against it. All 114 need access to the machine before they are reachable, 112 of them local and two physical, so none of this is a remote drive-by.
The bulletin now tells owners where to get the update. For two days and six hours it told them nothing.