# Hotfix vs Patch: What NIST's Glossary Says

Canonical: https://patchmanagementpolicy.com/guides/hotfix-vs-patch/
Last reviewed: 19 Nov 2026

## Hotfix vs patch

NIST's glossary, read 19 Nov 2026, defines hotfix as "Microsoft's term for 'patch'" (from SP 800-44 Version 2). For a policy the two words name one thing, so one definition of patch and one deadline by severity cover both. Microsoft's own terminology page names four packages, not a separate hotfix.

### What NIST's glossary defines

| Term | NIST glossary definition (quoted) | Source document named |
|---|---|---|
| Hotfix | "Microsoft's term for 'patch.'" | NIST SP 800-44 Version 2 |
| Patch | "A 'repair job' for a piece of programming; also known as a 'fix.'" It is "the immediate solution that is provided to users"; developers "often find a better solution to provide when they package the product for its next release." | NIST SP 800-44 Version 2 and SP 800-45 Version 2 |
| Patch | "Software component that, when installed, directly modifies files or device settings related to a different software component without changing the version number or release details for the related software component." | CNSSI 4009-2022, from ISO/IEC 19770-2:2015 |

NIST CSRC glossary entries for hotfix and patch, read 19 Nov 2026 (csrc.nist.gov/glossary). Label: primary.

The glossary does not define hotfix independently: the whole entry is the phrase quoted in the table. The answer to the question in the title, as far as a primary source goes, is that a hotfix is a patch under a Microsoft name.

### Where the two patch definitions differ

The CNSSI definition carries a test: a patch leaves the version number and release details of the related software unchanged. Many vendor fixes arrive as a new version or a cumulative package. Microsoft's standard terminology page defines an update rollup as "a tested, cumulative set of hotfixes, security updates, critical updates, and updates," and its quality update page says security updates are "typically released on the second Tuesday of each month, though they can be released at any time" ([Microsoft Learn](https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/standard-terminology-software-updates)). A policy that defined patch by the CNSSI test would leave out a package that changes the version number.

The SP 800-44 wording points the other way: the patch is the immediate fix and may later be replaced by a better solution in the next release. For a deadline, that matters because the window runs from the vendor's release of the fix, whatever its name or whether the version number moves.

### The definition to write into the policy

Suggested definition: **Patch.** Any vendor-released change to software or firmware that fixes a flaw, including a security update, hotfix, update rollup, service pack, firmware update or out-of-band release. A deadline in section 4 attaches to the flaw's severity, whatever the package is called and whether or not it changes the version number.

On 19 Nov 2026 Microsoft's terminology page defined security update, update, update rollup and service pack, and the word hotfix appeared only inside the rollup and service pack definitions. A non-security update, which Microsoft describes as a fix for a "noncritical, non-security-related bug," can go on the monthly maintenance window without a severity deadline. The [glossary](https://patchmanagementpolicy.com/glossary/) and [policy sections](https://patchmanagementpolicy.com/policy-sections/) carry the surrounding wording, and [how often to patch](https://patchmanagementpolicy.com/guides/how-often-to-patch/) sets the cadence for each source. Other short definitions are answered in the [FAQ](https://patchmanagementpolicy.com/faq/).

### Sources

- [NIST CSRC Glossary, hotfix (source: NIST SP 800-44 Version 2)](https://csrc.nist.gov/glossary/term/hotfix), read 19 Nov 2026
- [NIST CSRC Glossary, patch (sources: CNSSI 4009-2022, SP 800-44 Version 2, SP 800-45 Version 2)](https://csrc.nist.gov/glossary/term/patch), read 19 Nov 2026
- [Microsoft Learn, Standard terminology for software updates](https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/standard-terminology-software-updates), read 19 Nov 2026
- [Microsoft Learn, Windows quality updates quick start](https://learn.microsoft.com/en-us/windows/deployment/update/waas-quick-start), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [How Often to Patch: Cadences From the Clauses Read](https://patchmanagementpolicy.com/guides/how-often-to-patch/)
- [Patch Management Glossary: 32 Terms, Sourced](https://patchmanagementpolicy.com/glossary/)
- [Patch Management Policy Sections: The Nine to Include](https://patchmanagementpolicy.com/policy-sections/)
- [What Is Patch Management? Definition and Scale in 2026](https://patchmanagementpolicy.com/guides/what-is-patch-management/)
