> For the complete documentation index, see [llms.txt](https://run-ai-docs.nvidia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://run-ai-docs.nvidia.com/self-hosted/getting-started/whats-new/hotfixes-for-version-2.26.md).

# Hotfixes for Version 2.26

This section provides details on all hotfixes available for version 2.26. Hotfixes are critical updates released between our major and minor versions to address specific issues or vulnerabilities. These updates ensure the system remains secure, stable, and optimized without requiring a full version upgrade.

<table><thead><tr><th width="113.9140625">Version</th><th width="130.42578125">Date (MM/DD/YYYY)</th><th width="118.6171875">Internal ID</th><th>Description</th></tr></thead><tbody><tr><td>2.26.33</td><td>08/05/2026</td><td>RUN-41143</td><td>Fixed an issue where selecting a single node pool for a Project in the UI was not saved, causing the Project to inherit node pools from the parent Department instead.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41720</td><td>Fixed an issue where inference throughput and latency metrics stopped updating cluster-wide when a Knative 1.19+ inference pod emitted more than one HTTP status code.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41566</td><td>Fixed an issue where the device plugin failed to register with kubelet when devicePluginBindings was enabled, preventing GPU resources from being advertised to the cluster.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41489</td><td>Fixed an issue where fractional GPU preloaders caused certain applications to crash on startup in fractional GPU workloads.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41161</td><td>Fixed an issue where workloads with endpoint access set to "Specific users and service accounts" became stuck.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41563</td><td>Fixed a security vulnerability (GHSA-xhf5-7wjv-pqxp, severity: High) in the application-controller service.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41140</td><td>Fixed an issue in Nodes > Pod View where the pagination total included historical pods while the table displayed only active pods.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41486</td><td>Fixed a security vulnerability related to CVE-2026-42530 with severity HIGH.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41514</td><td>Fixed an issue where the tool connection URL returned 404 on Training and Workspace workloads when path-based routing was enabled.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41445</td><td>Fixed an issue where the upgrade migration job failed with an ImagePullBackOff error on self-hosted installations.</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41378</td><td>Fixed an issue where email notification delivery stopped working after upgrading when the SMTP authentication type was set to "None".</td></tr><tr><td>2.26.27</td><td>07/30/2026</td><td>RUN-41210</td><td>Fixed an issue where workload status change email notifications were sent with blank content.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://run-ai-docs.nvidia.com/self-hosted/getting-started/whats-new/hotfixes-for-version-2.26.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.