CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Called exploited the same day it was disclosed.
Measured from the CVE publication date to the earliest of 3 KEV catalogues that list it.
The life of this vulnerability
- CVE published
- First KEV listingsame day
- Last sighting9d
Gaps are compressed to equal steps. The elapsed time is printed under each.
Which catalogues call it exploited
- CISA KEVUS federallisted Jul 29, 2026
- EUVDENISA, European Unionlisted Jul 29, 2026
- VulnCheck KEVcommercial researchlisted Jul 29, 2026
- CIRCLaggregator, mirrors the abovelisted Jul 29, 2026, not counted
3 catalogues list it. CIRCL aggregates the others and is shown but not counted.
Public exploitation evidence
- reported exploitationcydome.io/maritime-cybersecurity-bulletin-august-7th-2026/
- reported exploitationwww.recordedfuture.com/blog/july-2026-cve-landscape
- reported exploitationblackpointcyber.com/blog/blackpoint-soc-threat-pulse-week-of
- reported exploitationx.com/Horizon3ai/status/2083303075666600261#m
- reported exploitationprevidian.com/CVE-2026-20316
- reported exploitationsec.cloudapps.cisco.com/security/center/content/CiscoSecurit
7 public reports collected from VulnCheck and CIRCL, first on Jul 29, 2026. Each links to its original source. We have not verified them.
Description
A vulnerability in the web interface of Cisco Secure Firewall Management Center (FMC) Software could allow an unauthenticated, remote attacker to log in to an affected device using a low-privileged account to access sensitive data within the impacted systems. This vulnerability is due to the presence of static user credentials for a low-privileged account. An attacker could exploit this vulnerability by using the account to log in to an affected system. A successful exploit could allow the attacker to log in to the affected system and access sensitive data as the low-privileged user. Note: If the FMC management interface does not have public internet access, the attack su
Required action (CISA)
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). 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.
