[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5ov7D9Zi02ltjQrQUMjHPDwkxqEcgeSaWiEMe4sHQC4":3},{"article":4,"iocs":50,"watch_terms":55,"solutions":56,"lesson":118},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":28,"category":29,"article_tags":32},"439f25e0-27c7-48b6-8871-9bdf5b8a0ef3","CISA Adds One Known Exploited Vulnerability to Catalog","cisa-adds-one-known-exploited-vulnerability-to-catalog-f58ef4","CISA has added one new vulnerability to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation. CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function Vulnerability This type of vulnerability is a frequent attack vector for malicious cyber actors and poses significant risks to the federal enterprise. Binding Operational Directive (BOD) 26-04: Prioritizing Security Updates Based on Risk establishes vulnerability management requirements for Federal Civilian Executive Branch (FCEB) agencies, updating BOD 22-01. BOD 26-04 reinforces the importance of the KEV Catalog and requires federal agencies to prioritize rapid remediation of high-risk vulnerabilities, specifically those identified by Common Vulnerabilities and Exposures (CVEs) listed in CISA’s Known Exploited Vulnerabilities (KEV) Catalog on publicly exposed assets that grant total control of the asset post-exploitation, while deferring action for lower-risk vulnerabilities. BOD 26-04 further establishes basic expectations for when agencies must check whether threat actors compromised the system before the patch was applied. While BOD 26-04 applies only to FCEB agencies, CISA encourages all organizations to adopt risk-based vulnerability management and prioritize remediation of KEV Catalog vulnerabilities. CISA will continue to add vulnerabilities to the catalog that meet the specified criteria. Aware of an exploited vulnerability not currently listed in the KEV Catalog? Submit for potential addition: KEV Nomination Form. Potential KEV additions must have a CVE ID, evidence of exploitation, and clear mitigation guidance.","CISA has added CVE-2026-20253, a Splunk Enterprise vulnerability, to its Known Exploited Vulnerabilities (KEV) Catalog due to evidence of active exploitation. This addition is tied to Binding Operational Directive (BOD) 26-04, which mandates federal agencies prioritize patching KEV-listed vulnerabilities on public-facing assets. CISA encourages all organizations to adopt similar risk-based vulnerability management practices.","CISA adds CVE-2026-20253 Splunk Enterprise vulnerability to KEV Catalog.","https:\u002F\u002Fwww.cisa.gov\u002Fnews-events\u002Falerts\u002F2026\u002F06\u002F18\u002Fcisa-adds-one-known-exploited-vulnerability-catalog",null,"2026-06-18T12:00:00+00:00","2026-06-18T18:00:17.748291+00:00",8,[17,20,23,26],{"name":18,"type":19},"Splunk Enterprise","product",{"name":21,"type":22},"Splunk","vendor",{"name":24,"type":25},"vulnerability management","technology",{"name":27,"type":22},"CISA","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":28,"icon":12,"name":30,"slug":31},"Vulnerabilities","vulnerabilities",[33,38,40,45],{"category":34},{"id":35,"icon":12,"name":36,"slug":37},"217d3263-c763-41ca-875e-06901f522fe0","NIST","nist",{"category":39},{"id":28,"icon":12,"name":30,"slug":31},{"category":41},{"id":42,"icon":12,"name":43,"slug":44},"c5c77cdb-f7d7-4990-9436-c81dcbff1163","Policy","policy",{"category":46},{"id":47,"icon":12,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[51],{"type":52,"value":53,"context":54},"cve","CVE-2026-20253","Splunk Enterprise Missing Authentication for Critical Function Vulnerability",[21,27,18],{"controls":57,"vendors":112},[58,87],{"slug":59,"name":60,"problem":61,"products":62},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[63,71,79],{"vendor_slug":64,"vendor_name":65,"vendor_logo":66,"product_slug":67,"product_name":68,"url":69,"description":70},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"vendor_slug":72,"vendor_name":73,"vendor_logo":74,"product_slug":75,"product_name":76,"url":77,"description":78},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"vendor_slug":80,"vendor_name":81,"vendor_logo":82,"product_slug":83,"product_name":84,"url":85,"description":86},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"slug":88,"name":89,"problem":90,"products":91},"patch-management","Automated patch management","Known holes get closed in days, not months.",[92,100,108],{"vendor_slug":93,"vendor_name":94,"vendor_logo":95,"product_slug":96,"product_name":97,"url":98,"description":99},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":101,"vendor_name":102,"vendor_logo":103,"product_slug":104,"product_name":105,"url":106,"description":107},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":72,"vendor_name":73,"vendor_logo":74,"product_slug":88,"product_name":109,"url":110,"description":111},"Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",[113],{"slug":114,"name":21,"logo_path":115,"roles":116},"splunk","\u002Fvendor-logos\u002Fsplunk.png",[117],"affected",{"slug":119,"title":120,"body":121,"framework_refs":122,"framework_notes":131},"cisa-flags-actively-exploited-splunk-enterprise-vulnerability-patch-now","CISA Flags Actively Exploited Splunk Enterprise Vulnerability — Patch Now","CVE-2026-20253 in Splunk Enterprise has been added to CISA's Known Exploited Vulnerabilities Catalog, confirming active exploitation in the wild. This matters because Splunk is widely deployed as a core security monitoring platform, meaning a compromised instance could blind defenders and expose sensitive log data across an entire organization. CISA's Binding Operational Directive BOD 26-04 compels federal agencies to prioritize patching KEV-listed vulnerabilities on public-facing assets, but the risk extends equally to private sector organizations. Delayed patching of actively exploited vulnerabilities dramatically narrows the window between exposure and a successful breach.",[123,124,125,126,127,128,129,130],"CIS Control 7 - Continuous Vulnerability Management","CIS Control 2 - Inventory and Control of Software Assets","NIST SP 800-40 Rev. 4 - Guide to Enterprise Patch Management","NIST CSF ID.RA-1 - Asset vulnerabilities are identified and documented","NIST CSF RS.MI-3 - Newly identified vulnerabilities are mitigated or documented as accepted risks","CISA BOD 26-04 - Reducing the Significant Risk of Known Exploited Vulnerabilities","NIST SP 800-53 SI-2 - Flaw Remediation","ITIL 4 - Change Enablement \u002F Emergency Change procedures",{}]