Cyber Resilience

CWE · MITRE source

CWE-798Use of Hard-coded Credentials

Abstraction: Base · CVEs in our corpus: 1,784

The product contains hard-coded credentials, such as a password or cryptographic key.

There are two main variations:

Last updated: 22 August 2026 00:25 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: partial · 3 mapping(s) from 2 framework(s): CAPEC 2 (partial) · CSF 2.0 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A07:2025 Authentication Failures.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • SA-12 Supply Chain Protection
  • SA-13 Trustworthiness
  • SA-21 Developer Screening
  • SA-3 System Development Life Cycle
Detect
Catch it (CSF Detect / Respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)

NIST 800-53 r5 controls that address this weakness (21)AI-assisted

Showing the 15 most specific. Generic controls that address many weakness types are collapsed below.

Control Title Family Why it addresses this CWE
SA-12Supply Chain ProtectionSASupplier evaluation and secure acquisition practices make it harder for hard-coded credentials to be introduced via procured products.
SA-13TrustworthinessSAReduces hard-coded credentials by requiring that trustworthiness evidence includes absence of embedded secrets that bypass normal authentication.
SA-21Developer ScreeningSAVetting reduces the chance a developer will deliberately insert hard-coded credentials as a backdoor or unauthorized access mechanism.
IA-1Policy and ProceduresIAPolicy and procedures prohibit hard-coded credentials in favor of managed authentication.
IA-13Identity Providers and Authorization ServersIAExternal identity providers eliminate the need for hard-coded credentials in applications.
IA-5Authenticator ManagementIAChanging default authenticators prior to first use and protecting content prevents use of hard-coded credentials.
PM-16Threat Awareness ProgramPMIntelligence programs surface reports of campaigns that abuse hard-coded credentials in products, prompting removal or replacement and thereby reducing successful exploitation.
PM-3Information Security and Privacy ResourcesPMPlanned investment enables secure credential storage and management systems instead of hard-coded credentials.
PM-30Supply Chain Risk Management StrategyPMStrategy enforces supplier requirements and code reviews that reduce hard-coded credentials introduced through acquired products.
SR-1Policy and ProceduresSRPolicy and procedures require review of procured products for hard-coded credentials, reducing the chance they are introduced via the supply chain.
SR-6Supplier Assessments and ReviewsSRSupplier risk reviews identify and discourage hard-coded credentials in delivered products or services.
AC-9Previous Logon NotificationACEnables users to notice when hard-coded credentials have been exploited for unauthorized access.
AT-3Role-based TrainingATSecurity training explicitly warns against hard-coded credentials, lowering their use in systems.
PL-9Central ManagementPLCentral credential stores and rotation policies remove the need for hard-coded credentials in configuration files or code.
PS-2Position Risk DesignationPSVetting individuals before they occupy roles that touch credentials or secrets reduces the likelihood of hard-coded credentials being introduced or abused.
Show 6 more broadly-applicable controls
SA-3System Development Life CycleSAIntegrating risk management and security responsibilities into the SDLC makes use of hard-coded credentials visible during design and code reviews, reducing their introduction.
SA-4Acquisition ProcessSARequiring security functional requirements and acceptance criteria allows contracts to prohibit hard-coded credentials in delivered systems or components.
SA-5System DocumentationSAKnown vulnerabilities section of admin docs covers hard-coded credentials and how to replace them, limiting their use in deployments.
RA-10Threat HuntingRAAnomalous use of hard-coded credentials can be uncovered through behavioral and log analysis during hunts.
SC-38Operations SecuritySCMakes hard-coded credentials less likely by requiring OPSEC treatment of authentication material as protected information throughout development.
SI-5Security Alerts, Advisories, and DirectivesSIAdvisories about products containing hard-coded credentials allow organizations to apply mitigations or avoid affected components before exploitation.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2026-22769 KEV10.010.00.13122026-02-17
CVE-2017-14143 9.99.80.75502017-09-19
CVE-2019-1619 9.99.80.82822019-06-27
CVE-2019-1935 9.99.80.83392019-08-21
CVE-2019-15975 9.99.80.96462020-01-06
CVE-2019-15976 9.99.80.92842020-01-06
CVE-2020-8657 KEV 9.99.80.91872020-02-06
CVE-2020-13166 9.99.80.77632020-05-19
CVE-2020-11854 9.99.80.74452020-10-27
CVE-2022-26138 KEV 9.99.80.98172022-07-20
CVE-2023-6448 KEV 9.99.80.02092023-12-05
CVE-2024-3272 KEV 9.99.80.98042024-04-04
CVE-2024-3408 9.99.80.77952024-06-06
CVE-2024-20439 KEV 9.99.80.92062024-09-04
CVE-2025-14611 KEV9.99.80.53302025-12-12
CVE-2016-1560 9.89.80.72292017-04-21
CVE-2014-9614 9.89.80.68712020-02-19
CVE-2020-4429 9.89.80.71362020-05-07
CVE-2023-22463 9.89.80.69672023-01-04
CVE-2023-5074 9.89.80.67912023-09-20
CVE-2021-22707 9.79.80.64612021-07-21
CVE-2023-28503 9.69.80.62142023-03-29
CVE-2018-9161 9.59.80.57342018-03-31
CVE-2024-28987 KEV 9.59.10.93212024-08-21
CVE-2022-1162 9.49.10.76182022-04-04