This entry has been deprecated because it was too specific. Please refer to the broader and more comprehensive CWE-532: Information Exposure Through Log Files for current guidance.
This weakness was originally created to describe a specific scenario where sensitive information could be exposed through log files created during cleanup or maintenance processes. However, it was merged into a more general category because the core vulnerability—leaking data through any application log—is the same, regardless of when the log file was created. For developers, the key takeaway is that any log file, including temporary debug logs, installation logs, or cleanup reports, must be treated with the same security considerations as your main application logs. Always sanitize sensitive data (like passwords, keys, or PII) before writing to any file, and restrict access to log directories as part of your standard deployment configuration.