Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Automated vulnerability management uses continuous scanning, risk-based prioritization, and orchestrated remediation workflows to identify, assess, and fix security weaknesses with minimal manual intervention.

The browser is the operating environment for modern work — it’s where employees access email, SaaS applications, collaboration tools, HR systems, finance platforms, customer data, developer resources and AI services. All of this activity makes the browser a high-value target for attackers because it sits between users, identities, applications, and sensitive enterprise data.

This article was authored by Cristhian Parrot from the Kroll Offensive Security Team. Kroll’s Offensive Security Team recently discovered a new vulnerability within Microsoft’s Azure Monitor Agent Metrics Extension, which demonstrates how subtle configuration issues can introduce significant security risks in widely deployed infrastructure components.

brace-expansion is a very popular npm package with over 38 billion all-time downloads (yeah, over 38,000,000,000) and used by tooling almost every JavaScript project relies on - eslint, glob, and npm itself. Despite being in the public eye for a while, we found a new Denial-of-Service vulnerability that could affect millions. This post walks through what the package does, existing issues that were fixed, and the new one we found - CVE-2026-13149.

Modern exposure management has evolved beyond vulnerability scanning and alert volume into a discipline focused on measurable risk reduction. As the exposure management market matures, security leaders are adopting cyber exposure management platforms that unify signals across vulnerability, cloud, application, and attack surface tools to prioritize what truly matters.

We ran 300 vulnerability-finding scans to measure how repeatable an agentic LLM security review is on the same code, prompt, and harness. The headline result is not that one scanner "wins" a self-referential leaderboard. It is that LLM security findings are unevenly repeatable: reference-matched findings were stable, but extra-model reports varied widely from run to run.

Prepared for: Corporate cybersecurity blog publication Last verified: 2026-06-27 Scope: Defensive analysis only; no exploit payloads, shell commands, or operational PoC steps are included. Primary sources: TP-Link advisory, CVE.org, NVD, FIRST EPSS, CISA KEV feed, MITRE CWE/ATT&CK.

Network vulnerability management is no longer a periodic security task. As networks expand across locations, vendors, and OSs, vulnerabilities can emerge quietly through configuration changes, outdated firmware, or delayed patching. Without consistent visibility and automation, teams often discover risks only after they affect availability, security, or compliance. Effective vulnerability management requires continuous awareness, structured assessment, and controlled remediation.

For over twenty years, the global security community has operated under a single, comfortable assumption: that a centralized public source could help track, analyze, and enrich the world’s software vulnerabilities at the pace the industry needed. When the National Vulnerability Database (NVD) was established, the open source vulnerability lifecycle moved at a radically different pace.