# FedRAMP 2026 Patch Timeframes: 12 Hours to 192 Days

Canonical: https://patchmanagementpolicy.com/patch-windows/fedramp/
Last reviewed: 19 Nov 2026

## FedRAMP patching requirements

FedRAMP's Consolidated Rules for 2026 set maximum timeframes from 12 hours to 192 days by certification Class, impact level and exploitability, and follow CISA's KEV due dates. Initial and ongoing certification must meet them from 7 Dec 2026, with a grace period to 7 Mar 2027. Read 19 Nov 2026.

### Status and dates

The FedRAMP rules for Vulnerability Detection and Response (VDR) launched on 24 Jun 2026 and are marked "Required (Mandated by CISA BOD 26-04)." The page lists optional adoption from 4 Jul 2026, initial and ongoing certification from 7 Dec 2026, and a grace period ending 7 Mar 2027. FedRAMP's public notice [NTC-0014](https://www.fedramp.gov/notices/0014/) explains the move: mandatory adoption had been planned for 1 Jun 2027 with a grace period to 1 Jan 2028, and BOD 26-04 "makes it clear" that CISA will not wait. The notice also says the legacy monthly vulnerability scanning process "is insufficient." During the grace period, offerings not yet following the rules "may maintain their FedRAMP Certification under a corrective action plan (which will include notice to all agencies)," and after 7 Mar 2027 certification "will be revoked for all cloud service offerings not following these rules." The notice also reminds providers that the timeframes are "maximum timeframes" and that providers "should mitigate and/or remediate vulnerabilities much faster."

Control mappings were last updated on 13 Oct 2026, when the page records adding SI-2(3) to the timeframe rule; the earlier 1 Jul 2026 entry notes no change to the requirement.

### The timeframe rule

Rule VDR-TFR-PVR says providers "SHOULD partially mitigate vulnerabilities, fully mitigate vulnerabilities, or remediate vulnerabilities to a lower potential agency impact within the timeframes from evaluation shown below," factoring in the Potential Agency Impact "N-rating" (PAIN), internet reachability and likely exploitability. The days are maxima. The Class A and Class B tables are identical.

| PAIN level and column | Class A and B | Class C | Class D |
|---|---|---|---|
| PAIN-5, LEV + IRV | 4 days | 2 days | 12 hours |
| PAIN-5, LEV + NIRV | 8 days | 4 days | 1 day |
| PAIN-5, NLEV | 32 days | 16 days | 8 days |
| PAIN-4, LEV + IRV | 8 days | 4 days | 2 days |
| PAIN-4, LEV + NIRV | 32 days | 8 days | 8 days |
| PAIN-4, NLEV | 64 days | 64 days | 32 days |
| PAIN-3, LEV + IRV | 32 days | 16 days | 8 days |
| PAIN-3, LEV + NIRV | 64 days | 32 days | 16 days |
| PAIN-3, NLEV | 192 days | 128 days | 64 days |
| PAIN-2, LEV + IRV | 96 days | 48 days | 24 days |
| PAIN-2, LEV + NIRV | 160 days | 128 days | 96 days |
| PAIN-2, NLEV | 192 days | 192 days | 192 days |

FedRAMP Consolidated Rules for 2026, Rev5 path, VDR-TFR-PVR, timeframes from evaluation. Column labels are as printed on the page (LEV + IRV, LEV + NIRV, NLEV); the page text read does not expand them, so they are not expanded here. Read 19 Nov 2026.

Class D is the only table that uses hours: 12 hours for PAIN-5 where the column is LEV + IRV. The longest figure anywhere, 192 days, appears in all three tables.

### KEVs and everything else

- **VDR-TFR-KEV:** providers "SHOULD remediate Known Exploited Vulnerabilities according to the due dates in the CISA Known Exploited Vulnerabilities Catalog (even if the vulnerability has been fully mitigated)" as BOD 26-04 or successor guidance requires. FedRAMP sets no separate number; the [BOD 26-04 table](https://patchmanagementpolicy.com/patch-windows/cisa-bod-26-04/) governs.
- **VDR-TFR-RMN:** providers "SHOULD mitigate or remediate remaining vulnerabilities during routine operations as determined necessary by the provider." No number.
- **VDR-CSO-AKE:** providers "SHOULD NOT deploy or otherwise activate new machine-based information resources with Known Exploited Vulnerabilities."

### The older figures

FedRAMP's legacy playbook page on plans of action and milestones still reads: "FedRAMP requires Critical and High risks to be remediated within 30 days of discovery, Moderate risks within 90 days of discovery, and Low risks within 180 days of discovery." That text sits in the legacy documentation, not in the 2026 rules, and the 2026 VDR page does not mention 30, 90 or 180 days. The continuous monitoring strategy guide itself was not opened by name, so those three figures are attributed to the legacy page only.

### What a policy must write

1. Name the certification Class the cloud offering holds and copy the matching column of the timeframe table.
2. Define how Potential Agency Impact, internet reachability and likely exploitability are assigned to each finding, since the table cannot be applied without them.
3. Say that KEV-listed vulnerabilities follow the CISA due date and that a full mitigation does not end the remediation duty.
4. Say what is done for remaining vulnerabilities and who decides it is necessary.
5. State that failures in detection and response are themselves treated as vulnerabilities (rule VDR-CSO-FAV).

### Evidence

The VDR page frames the rules as continuous and automated: providers should "use automated services to improve and streamline vulnerability detection and response," and the page states the rules give flexibility in implementation "while ensuring agencies receive the information needed to support ongoing authorization decisions." The evidence is therefore the provider's evaluation records and timestamps compared with the table. FedRAMP's sibling Vulnerability Evaluation and Reporting rules, mandatory on the same date, cover how the evaluation and reporting are done and were not compared line by line here. A contractor-facing policy is in the [FedRAMP template](https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/); every date is in [dates to know](https://patchmanagementpolicy.com/dates-to-know/); row-level timing is in the [Patch Window Table](https://patchmanagementpolicy.com/patch-windows/).

### Sources

- [FedRAMP, Consolidated Rules for 2026, Rev5, Vulnerability Detection and Response](https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/), read 19 Nov 2026
- [FedRAMP, 20x path, Vulnerability Detection and Response (status dates)](https://www.fedramp.gov/2026/providers/20x/rules/vulnerability-detection-and-response/), read 19 Nov 2026
- [FedRAMP, Public Notice NTC-0014](https://www.fedramp.gov/notices/0014/), read 19 Nov 2026
- [FedRAMP, legacy playbook, POA&M remediation requirements](https://www.fedramp.gov/legacy/playbook/csp/authorization/poam/), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Patch Window Table: Deadlines in 12 Frameworks](https://patchmanagementpolicy.com/patch-windows/)
- [CISA BOD 26-04 Remediation Timelines, Row by Row](https://patchmanagementpolicy.com/patch-windows/cisa-bod-26-04/)
- [FedRAMP Patch Management Policy Template](https://patchmanagementpolicy.com/templates/federal-contractor-fedramp/)
- [Patch Management Compliance Dates: 7 Dec 2026 and Back](https://patchmanagementpolicy.com/dates-to-know/)
