Secure Error Logging Practices to Prevent Information Leaks Across Java, Kotlin, JavaScript and Python
Error logging forms a critical part of the software development lifecycle, aiding debugging and early detection of failures. However, logs must remain both informative and secure to avoid unintended information disclosure.
The article, written by Natalia Noyanova of T1 IT Holding, draws on years of experience in information security and static code analysis. It highlights how code analyzers flag internal or external information leaks tied to error logging and explains why fixing these issues requires more than simple code changes.
Logging levels range from DEBUG (detailed diagnostic data not used in production) through INFO, WARNING, ERROR to FATAL (critical errors that halt the application). Recording mechanisms include plain text files, multi-stage logs requiring special readers, binary formats and databases.
Trace ID provides a unique technical identifier generated at the API gateway for each incoming request and propagated unchanged through all microservices. Correlation ID links multiple technical requests that belong to one business transaction, such as an order placement involving inventory, payment and confirmation steps.
Examples of exploitation include Flask applications running with debug=True that return full stack traces revealing absolute paths like /app/main.py and Python interpreter versions. Similar leaks occur when developers manually return traceback.format_exc() or forward raw SQLite errors after failed queries, confirming the database engine and aiding SQL injection refinement.
Prevention measures cover removal of X-Powered-By and Server headers via Nginx server_tokens off, input sanitization with regular expressions to block newlines in trace identifiers, and adoption of OpenTelemetry for automatic generation of safe hex-formatted trace IDs. Structured JSON logging further isolates fields and prevents log injection attacks described under CWE-117.
Related articles
Cisco Releases Hotfixes for Actively Exploited CVE-2026-20316 Zero-Day in Secure FMC Allowing Static Credential Access
A zero-day vulnerability tracked as CVE-2026-20316 is being actively exploited in Cisco Secure Firewall Management Center, enabling remote attackers to authenticate using hardcoded low-privilege credentials without prior authentication. The flaw carries a CVSS score of 5.3 but has been elevated to High severity by Cisco due to its potential for chaining with other vulnerabilities to achieve privilege escalation. Cisco has issued hotfixes across multiple versions including 7.0, 7.2, 7.4, 7.6, 7.7 and 10.0 while urging administrators to inspect logs for the presence of /var/tmp/license.tmp as an indicator of compromise. The same indicator is also linked to the related critical authentication bypass CVE-2026-20079 that can lead to root access via script execution. Organizations are advised to restrict management interface exposure through ACLs, VPNs and dedicated admin networks, rotate credentials after suspected compromise, and review sudo executions and license-related commands. U.S. federal agencies have a remediation deadline of August 1, 2026 under the Known Exploited Vulnerabilities catalog.
Broadcom Patches Five Critical VMware Vulnerabilities Including CVSS 9.8 Authentication Bypass
Broadcom has released fixes for five vulnerabilities across multiple VMware products that could enable authentication bypass, remote code execution, and virtual machine escapes. The most severe issue, CVE-2026-59309 with a CVSS score of 9.8, resides in the VMware Directory Service component of vCenter and allows an attacker with network access to bypass authentication entirely. Successful compromise of vCenter grants control over hosts, virtual machines, networks, and storage, posing severe risks to enterprise environments. A second critical flaw, CVE-2026-47876, affects the VMXNET3 virtual adapter in ESX and permits an attacker with administrative privileges inside a guest VM to perform an out-of-bounds write and execute code on the hypervisor host. Additional patches address an unauthorized memory read in ESX, Workstation, and Fusion, along with insufficient logging that could conceal administrative actions. No workarounds exist, and administrators must apply the specified updates to vCenter, ESX, Cloud Foundation, Workstation, and Fusion.
Firefox JIT Vulnerability Exposes Tor Browser Users to Remote Code Execution
A high-severity flaw in Firefox's SpiderMonkey JavaScript engine allows remote code execution simply by visiting a malicious page, directly impacting Tor Browser users on unpatched versions. Registered as CVE-2026-10702, the vulnerability stems from incorrect memory handling in the JIT compiler that leaves a dangling reference to freed memory, enabling arbitrary read and write primitives. Researchers demonstrated successful exploitation that can compromise the browser's content rendering process and facilitate user deanonymization or OS-level attacks. The same issue served as the initial stage in the IonStack exploit chain against ARM64 Android devices, where it was chained with CVE-2026-43499 in the Linux kernel to achieve root privileges. Mozilla addressed the issue in Firefox 151.0.3, and the Tor Project rolled out corresponding fixes in Tor Browser 15.0.19, which also incorporates the latest Firefox ESR updates.
Google Releases Chrome Security Update Fixing 370 Vulnerabilities Including Seven Critical Issues
Google has issued a major security update for Chrome that addresses a total of 370 vulnerabilities across Windows, macOS, and Linux platforms. The update covers Chrome versions 151.0.7922.72 and 151.0.7922.71 and includes seven vulnerabilities rated Critical, the highest severity level. Among the critical flaws are multiple Use After Free issues affecting Compositing, Views, Skia, and Ozone components, plus input validation problems in Dawn and ANGLE graphics libraries and a race condition in the Updater component. In addition to the critical fixes, the release patches 71 High-severity vulnerabilities, 170 Medium-severity issues, and 122 Low-severity issues. The company plans a gradual rollout over the coming days and weeks. All listed CVEs from CVE-2026-17650 through CVE-2026-18019 have been resolved in this update.