Showing posts with label KEV. Show all posts
Showing posts with label KEV. Show all posts

Tuesday, August 18, 2026

CISA Adds VMware Vulnerability to KEV Catalog – 8-18-26

Today, CISA announced that it had added a path traversal vulnerability in the VMware vCenter (multiple VMware products are affected by the vulnerability) product to their Known Exploited Vulnerabilities (KEV) catalog. Broadcom previously disclosed the vulnerability and updated their advisory on August 3rd, 2026; they provide additional information here. The vulnerability was reported to Broadcom by Phil Brass and Matt South of Atredis Partners. Two separate Medium articles have reported public exploitation of the vulnerability:  

CISA has directed federal agencies to apply “mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. 

A compliance deadline of August 21st, 2026, has been established. 

Monday, July 27, 2026

CISA Adds FortiGuard Advisory to KEV Catalog – 7-27-26

This afternoon, CISA announced that it had added an exposure of sensitive information to an unauthorized actor vulnerability in the FortiGuard FortiOS product to their Known Exploited Vulnerabilities (KEV) catalog. FortiGuard reported the vulnerability on February 10th, 2026, and updated that advisory on March 12th, 2026. That advisory notes that: “Products that never had SSL-VPN enabled, are not impacted by this issue.”  

The vulnerability was originally reported by Peter Gabaldon from ITRESIT; that report includes proof-of-concept code. Gabaldon published additional information on the vulnerability discovery here. A separate exploit for the vulnerability was published by indoushka on February 16th, 2026. 

CISA has directed federal agencies using the affected FortiOS products to apply “mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements [Links added]. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable.” A compliance deadline of August 10th, 2026, has been set. 

Friday, July 17, 2026

CISA Adds 2 FortiGuard Vulnerabilities to KEV Catalog – 7-16-26

Yesterday, CISA announced that it had added two OS command injection vulnerabilities in the FortiGuard FortiSandbox product to the Known Exploited Vulnerabilities (KEV) catalog. 

CVE-2026-25089 – This vulnerability was previously reported by FortiGuard in June. FortiGuard has new versions that mitigate the vulnerability. 

CVE-2026-39808 – This vulnerability was previously reported by FortiGuard in April. FortiGuard has a new version that mitigates the vulnerability. The vulnerability was originally reported by Samuel de Lucas Maroto from KPMG Spain. Proof-of-concept code was published by Samu DeLucas on April 15th, 2026. 

CISA has directed federal agencies using the FortiSandbox product to apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. A compliance deadline of July 19th, 2026 has been established. 

Thursday, July 16, 2026

CISA Adds KNX Protocol Vulnerability to KEV Catalog – 7-15-26

Yesterday, CISA announced that it had added an overly restrictive account lockout mechanism vulnerability in the KNX Connection Authorization Protocol to the Known Exploited Vulnerability (KEV) catalog. The KNX Association previously disclosed the vulnerability in August of 2023. The KNX association provides generic set up suggestions to mitigate the vulnerability. 

The vulnerability was originally reported by Felix Eberstaller of Limes Security. The Limes Security Blog reported three campaigns {(2021 & 2023 here) and (2024 here)} exploiting the vulnerability. Limes reported having an unlock tool for affected devices. 

CISA has directed federal agencies using affected devices to apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. CISA has established a compliance deadline of July 26th, 2026. 

Tuesday, July 14, 2026

CISA Adds 2 Sonic Wall Vulnerabilities to KEV Catalog – 7-14-26

Today, CISA announced that it had added two vulnerabilities in the Sonic Wall SMA1000 Appliance Work Place interface. Sonic Wall disclosed the two vulnerabilities earlier today; noting that they had "investigated multiple cases indicating the active exploitation of the vulnerabilities described in this advisory.” Sonic wall has a new version that mitigates the vulnerabilities and provides indicators of compromise in their advisory. 

The two reported vulnerabilities are: 

  • Server-Side request forgery - CVE-2026-15409, and 
  • Code Injection - CVE-2026-15410 

CISA has directed federal agencies to apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04, Prioritizing Security Updates Based on Risk guidance, and CISA’s “Forensics Triage Requirements”. They were also told to follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. A compliance deadline of July 17th, 2026, has been established. 

 
/* Use this with templates/template-twocol.html */