Cyber Resilience

CWE · MITRE source

CWE-532Insertion of Sensitive Information into Log File

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

The product writes sensitive information to a log file.

Last updated: 22 August 2026 14:14 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 · 1 mapping(s) from 1 framework(s): CAPEC 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A09:2025 Security Logging and Alerting Failures.

Control responseHuman-reviewed

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

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • AU-1 Policy and Procedures
  • AU-13 Monitoring for Information Disclosure
  • AU-16 Cross-organizational Audit Logging
  • CM-13 Data Action Mapping
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 (9)AI-assisted

Control Title Family Why it addresses this CWE
AU-1Policy and ProceduresAUProcedures mandate excluding sensitive data from logs to prevent unauthorized exposure via audit records.
AU-13Monitoring for Information DisclosureAUIdentifies insertion of sensitive data into logs, allowing detection of unauthorized disclosure.
AU-16Cross-organizational Audit LoggingAUCross-organizational coordination enables agreement on what data to include in audit logs, directly reducing insertion of sensitive information.
CM-13Data Action MappingCMIdentifying logging as a data action allows prevention of sensitive information being inserted into log files.
IR-9Information Spillage ResponseIRThe process of identifying and eradicating spilled information applies directly to sensitive data inserted into log files.
PT-7Specific Categories of Personally Identifiable InformationPTSpecific processing rules for sensitive PII categories commonly include restrictions on logging, making insertion of such data into log files less likely.
RA-8Privacy Impact AssessmentsRAPIAs detect planned or existing logging of PII and require removal or protection, preventing insertion of sensitive information into logs.
SC-38Operations SecuritySCLimits insertion of sensitive operational details into logs by treating such data as key information requiring protection.
SI-15Information Output FilteringSIChecking application output against expected content catches insertion of sensitive values into log streams or files.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2018-11716 8.49.80.14292018-07-16
CVE-2020-35234 8.27.50.64602020-12-14
CVE-2018-11717 8.19.80.08582018-07-16
CVE-2023-43261 8.17.50.59342023-10-04
CVE-2024-20440 7.97.50.51902024-09-04
CVE-2017-7550 7.89.80.03562017-11-21
CVE-2018-17922 7.89.80.03242018-11-02
CVE-2019-3888 7.89.80.03032019-06-12
CVE-2026-22778 7.89.80.03722026-02-02
CVE-2017-7214 7.79.80.02302017-03-21
CVE-2017-8074 7.79.80.01942017-04-23
CVE-2017-6165 7.79.80.01922017-10-20
CVE-2018-1000060 7.79.80.02362018-02-09
CVE-2016-0898 7.710.00.01412018-03-29
CVE-2018-16049 7.79.80.02152018-10-03
CVE-2019-4008 7.79.80.02272019-02-07
CVE-2019-7612 7.79.80.02412019-03-25
CVE-2017-8075 7.69.80.01792017-04-23
CVE-2017-4955 7.69.80.01412017-06-13
CVE-2017-9615 7.69.80.01402017-06-26
CVE-2017-6709 7.69.80.01292017-07-06
CVE-2017-15366 7.69.80.01412017-10-26
CVE-2017-1000171 7.69.80.01382017-11-03
CVE-2018-1000123 7.69.80.01432018-03-13
CVE-2018-11320 7.69.80.01382018-05-21