On 2025-03-31, CISA added CVE-2024-20439 (Cisco Smart Licensing Utility) to its Known Exploited Vulnerabilities (KEV) catalog [2]. The vulnerability is listed in the catalog as "Cisco Smart Licensing Utility Static Credential Vulnerability" [2]. CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
CISA Adds Cisco Smart Licensing Utility Vulnerability CVE-2024-20439 to Known Exploited Vulnerabilities Catalog
1 min read
- Disclosed
- Mar 31, 2025
- Published
- Nov 10, 2026
- Last updated
- Nov 8, 2026
- CVSS basis
- Our assessment
- 97.1%, higher than 100% of CVEs
- Exploitation and patch status
- ExploitedKEV
- Attack vector
- Vulnerability status
- Actor type
- Motivation
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Government, Cross-industry
What to do nowOur advice
CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Timeline
Technical details
CISA KEV Listing Record
CISA added CVE-2024-20439 (Cisco Smart Licensing Utility) to the Known Exploited Vulnerabilities () catalog on 2025-03-31 [2].
Original Technical Description
Cisco Smart Licensing Utility contains a static credential vulnerability that allows an unauthenticated, remote attacker to log in to an affected system and gain administrative credentials. [2]
Official Required Action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. [2]
Individual Vulnerability Record
The U.S. National Vulnerability Database (NVD) provides an independent vulnerability record and description for CVE-2024-20439 [1].
References
Official / primary3
- [1]
“A vulnerability in Cisco Smart Licensing Utility (CSLU) could allow an unauthenticated, remote attacker to log into an affected system by using a static administrative credential. This vulnerability is due to an undocumented static user credential for an administrative account. An attacker could ”
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.