LIVE · cybersecurity feed
Live wire
Malware Hijacks Android Car Head UnitsCritical Flaw in NASA/JPL Open-Source Spacecraft Command Software Allowed Unauthenticated Command ExecutionCVE-2026-73570 · U.S. CISA adds Zimbra Collaboration Suite (ZCS) flaw to its Known Exploited Vulnerabilities catalogCVE-2024-3094 · Connecting the Dots: Securing the Overlooked Corners of the Software Development Lifecycle (SDLC) Supply Chain14 Trojanized npm Packages Drop RedC2 4.0 Linux Backdoor With AI-Assisted C2Hundreds of leaked AWS keys give full control over corporate accountsAndroid Car Malware Spreads Through Built-In Updaters for Ad Fraud, Proxy BotnetMalware injected into popular Rust packages to steal developer credentialsSix Maximum-Severity Flaws Found in Cisco ProductsCritical Isolated-vm Vulnerability Leads to RCE on Host
patch

Less panic patching, more precision

In this newsletter, Thor breaks down why you should stop relying solely on CVSS and start using EPSS and GCVE to focus your patching efforts on the threats that actually matter.

zeroday.news ·

Security teams are being urged to re-evaluate their vulnerability management strategies to better prepare for an anticipated surge in patching requirements. The current default practice of prioritizing vulnerabilities based solely on the Common Vulnerability Scoring System (CVSS) is insufficient, as CVSS measures theoretical severity rather than actual risk.

CVSS provides a score indicating how severe a vulnerability could be if exploited, but it does not account for the likelihood of exploitation. This means organizations may be dedicating resources to patching vulnerabilities with high theoretical impact but low real-world threat, while neglecting those actively being exploited.

A more effective approach involves integrating the Exploit Prediction Scoring System (EPSS) alongside CVSS. EPSS offers a probability score, ranging from 0 to 1, indicating the likelihood that a specific Common Vulnerability and Exposures (CVE) identifier will be exploited within the next 30 days. By combining a high CVSS score with a high EPSS score, organizations can identify critical vulnerabilities that demand immediate attention. Conversely, vulnerabilities with high CVSS scores but very low EPSS scores can potentially be deferred. This shift in triage logic can significantly reduce patch backlogs without compromising security posture.

Furthermore, understanding which vulnerabilities are actively being exploited is crucial. While CISA's Known Exploited Vulnerabilities (KEV) catalog is a valuable resource, its centralized nature and focus on U.S. federal visibility may not provide a comprehensive global perspective.

A decentralized approach, such as the emerging Global CVE (GCVE) initiative, offers a broader view. GCVE aims to accelerate the enrichment of vulnerability data, including exploit indicators and affected products, by allowing multiple sources of evidence to surface for a single CVE identifier. This decentralized model can deliver actionable context more rapidly than traditional pipelines, which have faced significant backlogs.

By pairing EPSS with CVSS and leveraging broader exploitation signals from initiatives like GCVE, security teams can develop a more informed and efficient vulnerability triage process. This probability-informed methodology, rather than one solely based on severity, allows for a more precise allocation of finite patching resources.

In related news, Cisco Talos has released EvidenceForge, an open-source tool designed to generate realistic, correlated synthetic security logs. This tool addresses the scarcity of high-quality, labeled datasets needed for training threat hunters and validating detection logic. EvidenceForge uses a unified event model and AI-assisted scenario authoring to ensure consistency across various log formats, injecting realistic background noise and causal sequencing to mimic real-world network environments without the complexities of using production data. Security teams can utilize EvidenceForge to build custom attack scenarios for training, testing SIEMs, and validating detection pipelines.

Separately, Cisco is adapting its own vulnerability disclosure practices to enhance the visibility of detailed technical information for vulnerabilities deemed critical, actively exploited, or having a higher likelihood of exploitation, particularly in the context of artificial intelligence.

patch
ShareXLinkedInWhatsAppFacebook

More News

view all →
malware

Hackers infect Android car head units with proxy botnet malware

A supply-chain attack targeting Android-based car head units is using a legitimate device-update app to spread malware that enlists compromised devices in a proxy botnet or uses them for ad fraud. [...]

security

Postal Service moves to finalize mail ballot regs before SCOTUS ruling

The rules have already been rejected by multiple state courts, but the Trump administration said it’s preparing in case of a favorable Supreme Court decision. The post Postal Service moves to finalize mail ballot regs before SCOTUS ruling appeared first on CyberScoop.

vulnerability

ToxicPanda 2.0 Gets a Major Upgrade, Expanding Attacks Across 16 Countries

ToxicPanda 2.0 targets 349 financial apps and abuses Android Wireless Debugging to gain deeper device access and steal banking credentials. ToxicPanda used to be a Europe-focused nuisance targeting a manageable list of banks. That version is gone. Zimperium’s zLabs team just documented ToxicPanda 2.0, and the numbers alone tell the story: 349 targeted financial institutions […]

ai

If you're not using AI to attack your own systems, your adversaries will

Agents are also the new attack surface - cue defenders' existential angst

privacy

TikTok Agrees to $400 Million Settlement in U.S. Child Privacy Lawsuit

TikTok has agreed to a $400 million settlement with the U.S. Department of Justice to resolve a lawsuit alleging violations of child privacy laws. The lawsuit, filed in 2024, accused the company of improperly collecting data from users under 13 and failing to comply with parental requests to delete accounts. The settlement includes an immediate payment of $300 million and an additional $100 million contingent on the dissolution of a prior consent decree related to Musical.ly.

security

Named Pipes Under Attack: Securing Windows Interprocess Communication

Windows named pipes provide fast interprocess communication, but weak access controls can expose privileged services to untrusted processes. ThreatLocker explains how endpoint verification, command authorization, strict input validation, and narrowly scoped privileges can help secure named-pipe communication. [...]