All news with #log4j tag

Tens of Millions Download Vulnerable Log4j (Log4Shell)

🛡️ Sonatype reports that 13% of Log4j downloads in 2025 — roughly 40 million of 300 million Maven Central downloads analyzed — remain vulnerable to the CVSS 10.0 Log4Shell flaw first disclosed four years ago. The vendor describes this as corrosive risk, where fixes exist but unsafe versions continue to spread because consumers don’t upgrade or transitive dependencies reintroduce bad releases. Sonatype highlights noisy SCA alerts, set-and-forget dependencies and poor selection criteria as root causes. It urges using SCA and artifact repositories to map exposure, automating upgrade PRs, enforcing repository guardrails and adopting new metrics to reduce unnecessary risk.

CTEM Focus: Prioritization and Validation in Practice

🔒 Continuous Threat Exposure Management (CTEM) reframes vulnerability work by centering on prioritization and validation instead of treating every scanner finding as equally urgent, helping teams stop chasing volume and start addressing exposures that actually endanger the business. Prioritization ranks issues by real business impact, while validation — via Adversarial Exposure Validation (AEV) technologies like breach and attack simulation and automated penetration testing — proves which gaps are exploitable. This converts assumptions into evidence and enables focused, continuous defense for dynamic environments.