Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

The promise of AI-driven development is speed. But security teams face a binary choice: slow down the AI train to ensure safety, or let it run wild and accumulate risk. At Snyk, we believe you shouldn't have to choose.

Security teams are frequently asked to provide clear, time-bounded evidence of their organization’s security posture. Whether the request comes from external auditors validating SOC 2, ISO 27001, PCI DSS, or internal governance reviews, they typically require collecting vulnerability data from multiple tools, reconciling resource lists, and manually generating spreadsheets for auditors. This process is slow, error-prone, and difficult to repeat consistently.

Every CVE starts as a vulnerability claim, but not every claim ends in agreement. Between researchers racing to disclose vulnerabilities, and open-source maintainers guarding the stability and reputation of their projects, a gray zone appears where “vulnerability” becomes a matter of debate. This is the story of many disputed CVEs. Where “vulnerability” is rarely a yes-or-no answer.

Threat and vulnerability management (TVM) is a continuous, risk-based cybersecurity discipline that combines vulnerability assessment with threat intelligence to identify, prioritize, and remediate security weaknesses before attackers can exploit them. Rather than treating vulnerability scanning and threat detection as separate activities, TVM integrates both into a unified lifecycle that connects visibility, context, action, and validation.

CVE-2026-1731 is a vulnerability disclosed in products developed by BeyondTrust. At the time of writing, publicly available technical details regarding the root cause, vulnerable code paths, and exploitation prerequisites remain limited. Based on initial advisory information, the issue affects components involved in privileged access or remote access workflows, which are typically deployed to manage high-value credentials, session brokering, or secure administrative access to enterprise systems.

Since our previous security bulletin, Arctic Wolf has observed malicious activities in the wild tied to suspected exploitation of CVE-2026-1731 of self-hosted BeyondTrust Remote Support and Privileged Remote Access deployments. We are sharing threat intelligence related to this activity to help defenders protect against this campaign. CVE-2026-1731 allows unauthenticated remote threat actors to execute operating system commands in the context of the site user via specially crafted requests.

For most engineering teams, AI feels like a breakthrough years in the making. Code gets written faster, reviews move quicker, and releases that once took weeks now happen in days—or even hours. But as more of the software lifecycle becomes automated, a less comfortable reality is setting in: application security hasn’t kept pace, and AI-native security practices are often missing. When AppSec foundations are immature, AI doesn’t reduce risk—it scales it.

Security teams are facing an attack surface that changes faster than it can be fully understood. Cloud adoption, Software-as-a-Service sprawl, and continuous delivery cycles have dissolved the traditional perimeter, replacing it with an environment where assets change with little notice. Shadow IT, abandoned infrastructure, expired certificates, and misconfigured services quietly expand exposure, often outside formal ownership.

Exposure management has outgrown visibility. With 67M+ findings per year, the real challenge is execution at scale. The 2026 Exposure Action Report shows that risk clusters in predictable places, most exposure is operational (not novel), and meaningful risk reduction comes from consolidation, prioritization, and disciplined remediation workflows — not adding more tools.