CWE-798: Use of Hard-coded Credentials
1660 CVEs have CWE-798 as their primary weakness. 8 of them are in the CISA KEV catalog. The highest EPSS score among them is 98.241%.
The product contains hard-coded credentials, such as a password or cryptographic key.
Child of CWE-1391: Use of Weak Credentials
Mitigations
- Architecture and Design: For outbound authentication: store passwords, keys, and other credentials outside of the code in a strongly-protected, encrypted configuration file or database that is protected from access by all outsiders, including other local users on the same system. Properly protect the key (CWE-320). If you cannot use encryption to protect the file, then make sure that the permissions are as restrictive as possible [REF-7]. In Windows environments, the Encrypted File System (EFS) may provide some protection.
- Architecture and Design: For inbound authentication: Rather than hard-code a default username and password, key, or other authentication credentials for first time logins, utilize a first login mode that requires the user to enter a unique strong password or key.
- Architecture and Design: If the product must contain hard-coded credentials or they cannot be removed, perform access control checks and limit which entities can access the feature that requires the hard-coded credentials. For example, a feature might only be enabled through the system console instead of through a network connection.
- Architecture and Design: For inbound authentication using passwords: apply strong one-way hashes to passwords and store those hashes in a configuration file or database with appropriate access control. That way, theft of the file/database still requires the attacker to try to crack the password. When handling an incoming password during authentication, take the hash of the password and compare it to the saved hash. Use randomly assigned salts for each separate hash that is generated. This increases the amount of computation that an attacker needs to conduct a brute-force attack, possibly limiting the effectiveness of the rainbow table method.
- Architecture and Design: For front-end to back-end connections: Three solutions are possible, although none are complete. The first suggestion involves the use of generated passwords or keys that are changed automatically and must be entered at given time intervals by a system administrator. These passwords will be held in memory and only be valid for the time intervals. Next, the passwords or keys should be limited at the back end to only performing actions valid for the front end, as opposed to having full access. Finally, the messages sent should be tagged and checksummed with time sensitive values so as to prevent replay-style attacks.
Observed examples
- CVE-2022-40263: Software for biological cell analysis has hard-coded credentials, leading to leak of Protected Health Information (PHI)
- CVE-2022-29953: Condition Monitor firmware has a maintenance interface with hard-coded credentials
- CVE-2022-29960: Engineering Workstation uses hard-coded cryptographic keys that could allow for unauthorized filesystem access and privilege escalation
- CVE-2022-29964: Distributed Control System (DCS) has hard-coded passwords for local shell access
- CVE-2022-30997: Programmable Logic Controller (PLC) has a maintenance service that uses undocumented, hard-coded credentials
- CVE-2022-30314: Firmware for a Safety Instrumented System (SIS) has hard-coded credentials for access to boot configuration
- CVE-2022-30271: Remote Terminal Unit (RTU) uses a hard-coded SSH private key that is likely to be used in typical deployments
- CVE-2021-37555: Telnet service for IoT feeder for dogs and cats has hard-coded password [REF-1288]
- CVE-2021-35033: Firmware for a WiFi router uses a hard-coded password for a BusyBox shell, allowing bypass of authentication through the UART port
- CVE-2012-3503: Installation script has a hard-coded secret token value, allowing attackers to bypass authentication
- CVE-2010-2772: SCADA system uses a hard-coded password to protect back-end database containing authorization information, exploited by Stuxnet worm
- CVE-2010-2073: FTP server library uses hard-coded usernames and passwords for three default accounts
- CVE-2010-1573: Chain: Router firmware uses hard-coded username and password for access to debug functionality, which can be used to execute arbitrary code
- CVE-2008-2369: Server uses hard-coded authentication key
- CVE-2008-0961: Backup product uses hard-coded username and password, allowing attackers to bypass authentication via the RPC interface
- CVE-2008-1160: Security appliance uses hard-coded password allowing attackers to gain root access
- CVE-2006-7142: Drive encryption product stores hard-coded cryptographic keys for encrypted configuration files in executable programs
- CVE-2005-3716: VoIP product uses hard-coded public credentials that cannot be changed, which allows attackers to obtain sensitive information
- CVE-2005-3803: VoIP product uses hard coded public and private SNMP community strings that cannot be changed, which allows remote attackers to obtain sensitive information
- CVE-2005-0496: Backup product contains hard-coded credentials that effectively serve as a back door, which allows remote attackers to access the file system
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2022-26138 | 2022-07-20 | CRITICAL | 9.8 | 98.241% | The Atlassian Questions For Confluence app for Confluence Server and Data Center creates a Confluence user account in the confluence-users group with the… |
| CVE-2024-3272 | 2024-04-04 | CRITICAL | 9.8 | 98.109% | ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as very critical, has been found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to… |
| CVE-2024-28987 | 2024-08-21 | CRITICAL | 9.1 | 93.299% | The SolarWinds Web Help Desk (WHD) software is affected by a hardcoded credential vulnerability, allowing remote unauthenticated user to access internal… |
| CVE-2020-8657 | 2020-02-06 | CRITICAL | 9.8 | 91.874% | An issue was discovered in EyesOfNetwork 5.3. The installation uses the same API key (hardcoded as EONAPI_KEY in include/api_functions.php for API version… |
| CVE-2025-14611 | 2025-12-12 | CRITICAL | 9.8 | 54.534% | Gladinet CentreStack and Triofox prior to version 16.12.10420.56791 used hardcoded values for their implementation of the AES cryptoscheme. This degrades… |
| CVE-2021-44207 | 2021-12-21 | HIGH | 8.1 | 17.441% | Acclaim USAHERDS through 7.4.0.1 uses hard-coded credentials. |
| CVE-2026-22769 | 2026-02-17 | CRITICAL | 10.0 | 13.335% | Dell RecoverPoint for Virtual Machines, versions prior to 6.0.3.1 HF1, contain a hardcoded credential vulnerability. This is considered critical as an… |
| CVE-2019-6693 | 2019-11-21 | MEDIUM | 6.5 | 6.640% | Use of a hard-coded cryptographic key to cipher sensitive data in FortiOS configuration backup file may allow an attacker with access to the backup file to… |
| CVE-2026-122147 | 2026-11-17 | CRITICAL | 9.8 | not scored | ICRTouch PocketTouch version 1.700 build 2025.3726 defines hard-coded default values for multiple credential fields, including a socket password and… |
| CVE-2026-122055 | 2026-11-17 | CRITICAL | 9.8 | not scored | ICRTouch PocketTouch version 1.700 build 2025.3726 contains a default socket password set to the literal value password. Where the default value remains… |
| CVE-2026-130803 | 2026-11-17 | HIGH | 7.5 | not scored | The firmware and flash memory store critical cryptographic secrets, such as global AES keys and network master keys, in unencrypted formats. Additionally… |
| CVE-2026-100974 | 2026-11-17 | MEDIUM | 6.7 | not scored | NVIDIA OpenShell for Linux contains a vulnerability in the sandbox SSH authentication component where a remote attacker with high privileges could gain… |
| CVE-2026-123052 | 2026-11-17 | MEDIUM | 4.7 | not scored | The CeliachiaRL integration component distributed with Farmasimplex uses shared OAuth credentials across multiple customer installations. An attacker who… |
| CVE-2026-123051 | 2026-11-17 | LOW | 1.2 | not scored | The REV.exe module distributed with Farmasimplex contains embedded OAuth client credentials for integration with the IZS platform. An attacker with access to… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-798'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-798'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).