[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$frenTaCLuBersqVbG3_411tKDJAa3SAxcuZKZdgrDQDE":3},{"article":4,"iocs":50,"watch_terms":58,"solutions":59,"lesson":150},{"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},"1ba99e0c-207a-4acf-8ed5-dc6a34a23c3f","CISA Adds Two Known Exploited Vulnerabilities to Catalog","cisa-adds-two-known-exploited-vulnerabilities-to-catalog-7b5dac","CISA has added two new vulnerabilities to its Known Exploited Vulnerabilities (KEV) Catalog, based on evidence of active exploitation. CVE-2026-114713 UnrealIRCd Improper Neutralization of Delimiters Vulnerability CVE-2026-123039 Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability These types of vulnerabilities are a frequent attack vector for malicious cyber actors and pose 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. 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 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 it for potential addition through CISA’s KEV Nomination Form. Potential KEV additions must have a CVE ID, evidence of exploitation, and clear mitigation guidance.","CISA has added two new vulnerabilities, CVE-2026-114713 and CVE-2026-123039, to its Known Exploited Vulnerabilities (KEV) Catalog due to evidence of active exploitation. These vulnerabilities are identified as frequent attack vectors for malicious actors and pose significant risks to the federal enterprise. Binding Operational Directive (BOD) 26-04 requires federal agencies to prioritize remediation of KEV Catalog vulnerabilities on publicly exposed assets.","CISA adds two new exploited vulnerabilities to its KEV Catalog.","https:\u002F\u002Fwww.cisa.gov\u002Fnews-events\u002Falerts\u002F2026\u002F11\u002F13\u002Fcisa-adds-two-known-exploited-vulnerabilities-catalog",null,"2026-11-13T12:00:00+00:00","2026-11-13T21:00:12.083147+00:00",8,[17,20,23,26],{"name":18,"type":19},"Check Point","vendor",{"name":21,"type":22},"UnrealIRCd","product",{"name":24,"type":25},"CISA KEV Catalog","technology",{"name":27,"type":25},"Binding Operational Directive (BOD) 26-04","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":28,"icon":12,"name":30,"slug":31},"Vulnerabilities","vulnerabilities",[33,38,43,45],{"category":34},{"id":35,"icon":12,"name":36,"slug":37},"217d3263-c763-41ca-875e-06901f522fe0","NIST","nist",{"category":39},{"id":40,"icon":12,"name":41,"slug":42},"6cbdd207-aaa1-4176-9534-e156b125e917","Nation-state","nation-state",{"category":44},{"id":28,"icon":12,"name":30,"slug":31},{"category":46},{"id":47,"icon":12,"name":48,"slug":49},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[51,55],{"type":52,"value":53,"context":54},"cve","CVE-2026-114713","UnrealIRCd Improper Neutralization of Delimiters Vulnerability",{"type":52,"value":56,"context":57},"CVE-2026-123039","Check Point Multiple Products Incorrect Permission Assignment for Critical Resource Vulnerability",[18,21],{"controls":60,"vendors":144},[61,90,119],{"slug":62,"name":63,"problem":64,"products":65},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[66,74,82],{"vendor_slug":67,"vendor_name":68,"vendor_logo":69,"product_slug":70,"product_name":71,"url":72,"description":73},"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.",{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":78,"product_name":79,"url":80,"description":81},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"vendor_slug":83,"vendor_name":84,"vendor_logo":85,"product_slug":86,"product_name":87,"url":88,"description":89},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"slug":91,"name":92,"problem":93,"products":94},"patch-management","Automated patch management","Known holes get closed in days, not months.",[95,103,111],{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"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":104,"vendor_name":105,"vendor_logo":106,"product_slug":107,"product_name":108,"url":109,"description":110},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"vendor_slug":112,"vendor_name":113,"vendor_logo":114,"product_slug":115,"product_name":116,"url":117,"description":118},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"slug":120,"name":121,"problem":122,"products":123},"asset-inventory","Cyber asset inventory","You cannot patch, monitor or protect the devices, cloud resources and accounts you do not know you have.",[124,129,136],{"vendor_slug":75,"vendor_name":76,"vendor_logo":77,"product_slug":125,"product_name":126,"url":127,"description":128},"axonius-cyber-assets","Axonius Cyber Assets","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fcyber-assets","A continuously reconciled view of every asset, who owns it, which security controls cover it and where it drifts from policy.",{"vendor_slug":130,"vendor_name":131,"vendor_logo":132,"product_slug":133,"product_name":131,"url":134,"description":135},"lansweeper","Lansweeper","\u002Fvendor-logos\u002Flansweeper.png","lansweeper-asset-inventory","https:\u002F\u002Fwww.lansweeper.com\u002Fproduct\u002Fasset-inventory\u002F","Discovery with and without agents that keeps one central, always-updated inventory of devices, software and their details.",{"vendor_slug":137,"vendor_name":138,"vendor_logo":139,"product_slug":140,"product_name":141,"url":142,"description":143},"runzero","runZero","\u002Fvendor-logos\u002Frunzero.png","runzero-platform","runZero Platform","https:\u002F\u002Fwww.runzero.com\u002Fplatform\u002F","Finds and fingerprints everything on the network and in the cloud, including IoT and OT devices, without agents or credentials, and flags exposures.",[145],{"slug":146,"name":18,"logo_path":147,"roles":148},"check-point","\u002Fvendor-logos\u002Fcheck-point.png",[149],"affected",{"slug":151,"title":152,"body":153,"framework_refs":154,"framework_notes":160},"actively-exploited-vulnerabilities-added-to-cisa-kev-catalog-demand-immediate-remediation","Actively Exploited Vulnerabilities Added to CISA KEV Catalog Demand Immediate Remediation","CISA's addition of CVE-2026-114713 and CVE-2026-123039 to the Known Exploited Vulnerabilities Catalog confirms that threat actors are actively leveraging these flaws against real targets, including federal systems. When known vulnerabilities remain unpatched on publicly exposed assets, organizations hand attackers a documented, low-effort path into their networks. The KEV Catalog exists precisely because patch backlogs and poor asset visibility routinely allow exploitable conditions to persist long after fixes are available. Federal agencies are legally bound under BOD 26-04 to remediate KEV entries promptly, yet the continued exploitation of cataloged vulnerabilities signals that remediation timelines are still too slow across the broader ecosystem. Organizations of all types should treat KEV additions as urgent operational signals, not routine advisory notices.",[155,156,157,158,159],"CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 RS.MI-03: Newly identified vulnerabilities are mitigated or documented as accepted risks","NIS2 Article 21(2)(e)","CIS Control 1: Inventory and Control of Enterprise Assets (v8)",{"NIS2 Article 21(2)(e)":161,"NIST SP 800-53 SI-2: Flaw Remediation":162,"CIS Control 7: Continuous Vulnerability Management (v8)":163,"CIS Control 1: Inventory and Control of Enterprise Assets (v8)":164,"NIST CSF 2.0 RS.MI-03: Newly identified vulnerabilities are mitigated or documented as accepted risks":165},"NIS2 Article 21(2)(e) requires entities to handle vulnerability disclosure and security in system maintenance, obligating operators to remediate known exploited vulnerabilities as part of their ongoing security obligations.","SI-2 mandates that organizations identify, report, and correct system flaws within organizationally defined time periods, which is exactly what BOD 26-04 enforces for KEV-listed vulnerabilities on federal assets.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities, directly addressing the failure to patch actively exploited CVEs before or immediately after they appear in the KEV Catalog.","An accurate asset inventory is a prerequisite for knowing which systems are exposed to KEV-listed CVEs; without it, organizations cannot confirm whether affected software exists on publicly reachable hosts.","This category directly covers the expectation that once a vulnerability is confirmed as exploited and cataloged, the organization must act to mitigate it or formally accept and document the risk."]