Skip to content
Atesto
Create account
All articles

Audits and evidence

CISA adds six vulnerabilities and sets pre-patch check expectations

CISA added six vulnerabilities to its catalog and reinforced BOD 26-04 expectations for federal agencies to check for compromise before applying patches.

On October 20, 2026, the Cybersecurity and Infrastructure Security Agency (opens in a new tab) added six vulnerabilities to its Known Exploited Vulnerabilities Catalog. The addition triggers specific requirements under Binding Operational Directive 26-04. The directive establishes vulnerability management requirements for Federal Civilian Executive Branch agencies. It requires these agencies to prioritize the rapid remediation of high-risk vulnerabilities on publicly exposed assets. The directive also sets expectations for when agencies must check whether threat actors compromised a system before a patch was applied.

Checking for compromise before patching changes how IT teams handle remediation. A patch closes a vulnerability, but it does not remove an attacker who already used the vulnerability to access the network. When an agency checks for prior compromise, it generates logs and findings. This process creates an evidence trail. During an audit, organizations often need to prove that their systems are secure, not just patched.

Security questionnaires and SOC 2 audits frequently ask how an organization identifies and mitigates known vulnerabilities. Documenting the pre-patch state provides evidence that the remediation was complete. It shows auditors that no persistent threat remains on the asset. When an organization applies a security update, the standard evidence collected is often just a deployment log showing the patch version and the timestamp.

Binding Operational Directive 26-04 introduces a different expectation for federal agencies by requiring checks for prior compromise. This distinction matters for evidence collection. A patch deployment log only proves that the software was updated. It does not prove that the system was free of unauthorized access at the time of the update.

During a SOC 2 audit, auditors evaluate how an organization identifies, tracks, and mitigates known vulnerabilities. The auditor looks for evidence that the organization follows its stated policies. If a policy requires checking for compromise before patching, the organization must provide the logs or findings from that check. This provenance of evidence shows that the security team actively verified the integrity of the publicly exposed asset.

Customer security questionnaires also frequently ask vendors how they handle critical vulnerabilities. Enterprise customers want to know if their vendors monitor authoritative sources like the Known Exploited Vulnerabilities Catalog. When a vendor can provide documented evidence that they check for pre-patch compromise, they demonstrate a mature vulnerability management process. This level of documentation answers questionnaire items more thoroughly than a simple confirmation of patch deployment.

Who it applies to

Binding Operational Directive 26-04 applies directly to Federal Civilian Executive Branch agencies in the United States. The text establishes vulnerability management requirements specifically for these federal entities. The directive requires them to manage their publicly exposed assets according to its rules.

While the directive only binds federal agencies, the Cybersecurity and Infrastructure Security Agency encourages all organizations to adopt risk-based vulnerability management. The agency recommends that private companies prioritize the remediation of vulnerabilities listed in the catalog. IT service providers, global enterprises, and organizations managing sensitive data often use the Known Exploited Vulnerabilities Catalog as a baseline for their own security programs.

Chief Information Security Officers use the catalog to prioritize patching schedules because it serves as a definitive list of active threats. Aligning internal policies with federal directives helps companies provide standardized evidence to their auditors and enterprise customers.

What it requires

Binding Operational Directive 26-04 reinforces the importance of the Known Exploited Vulnerabilities Catalog. The directive requires federal agencies to prioritize the rapid remediation of high-risk vulnerabilities. This prioritization specifically targets vulnerabilities identified by Common Vulnerabilities and Exposures listed in the catalog. The requirement applies to publicly exposed assets that grant total control of the asset post-exploitation.

The directive allows agencies to defer action for lower-risk vulnerabilities. This ensures that resources focus on the most critical threats. Furthermore, the directive "establishes basic expectations for when agencies must check" whether threat actors compromised the system before the patch was applied, according to the agency.

The six vulnerabilities added to the catalog on October 20, 2026, include four affecting Plex Media Server. These are CVE-2026-96652, CVE-2026-96654, CVE-2026-96655, and CVE-2026-96656. The list also includes an OS command injection vulnerability in EG Secure Solutions SiteGuard Server Edition, identified as CVE-2026-106931. The final addition is an uncontrolled search path element vulnerability in Siemens Software Center, identified as CVE-2026-110936.

The agency notes that these types of vulnerabilities pose significant risks to the federal enterprise. They represent a frequent attack vector for malicious cyber actors. Documenting the remediation of these specific items, including the checks for prior compromise, builds a defensible security posture for audits.

The dates

The Cybersecurity and Infrastructure Security Agency added the six new vulnerabilities to the Known Exploited Vulnerabilities Catalog on October 20, 2026. The agency states that it will continue to add vulnerabilities to the catalog that meet its specified criteria. These criteria include having a CVE ID, evidence of exploitation, and clear mitigation guidance.

What to check now

  • Review vulnerability management policies to see how they address publicly exposed assets.
  • Scan external facing assets for the six specific vulnerabilities added to the catalog on October 20.
  • Verify whether IT procedures include checking for system compromise before applying security updates.
  • Document the results of pre-patch compromise checks to create an evidence trail for future security audits.
  • Confirm that customer security questionnaires accurately reflect how the organization uses the Known Exploited Vulnerabilities Catalog.
  • Store remediation logs and compromise check findings in a secure location accessible to compliance officers.

Security audits increasingly focus on the quality and provenance of evidence. Documenting the state of a system before a patch proves that the remediation addressed both the vulnerability and any potential active threats. Organizations that align their internal policies with federal directives build a stronger case for their security posture during external audits.

Sources

  1. Cybersecurity and Infrastructure Security Agency (opens in a new tab) · www.cisa.gov

This article is general information, not legal advice. For your company's situation, talk to a qualified lawyer.

This article was written with AI and checked, sentence by sentence, against the sources linked above.