The Common UNIX Printing System (CUPS) is a widely used printing system on Unix-like operating systems, but recent vulnerabilities have exposed significant risks. The most critical is CVE-2024-47176, which affects the cups-browsed service by binding to the IP address INADDR_ANY:631. This configuration flaw causes it to trust all incoming packets, leading to potential remote code execution when interacting with malicious printers. This vulnerability is part of a chain of exploits, including.

We’re thrilled to announce that we’ve been honored with the prestigious 2025 TrustRadius Buyer's Choice! This recognition is a testament to the hard work and dedication of WatchGuard’s team and validates our focus on product innovation and ongoing commitment to simplifying security for partners and customers.

Enterprises today rely on partners and vendors to help manage their data. Some companies depend on third-party infrastructure for day-to-day operations, so understanding the regulations and protection standards that a service provider is promising to uphold is very important.

In recent years, the security of the United States' critical infrastructure has become a pressing concern, particularly in the oil and gas sector, due to its pivotal role in the nation's economy and energy supply. Recognizing this, the Transportation Security Administration (TSA) implements several new directives in July each year aimed at enhancing the security and resilience of vital energy infrastructure against various threats, including cyber-attacks and physical disruptions.

Today, we’re thrilled to announce Jit’s certified integration with Wiz! This partnership will make it easier than ever for developers to consistently resolve security issues before production, and for security teams to unify and prioritize the top risks in production – effectively bridging the gap between the core objectives of ASPM and CNAPP. We believe that securing apps in the cloud has been overcomplicated by tool sprawl, alerting noise, and a disjointed UX for developers.

7 hours. That’s how long, on average, a developer takes to remediate a security issue in their code. Vulnerability detection is improving rapidly and scaling, but remediating security risks is still a tedious, time-consuming process that takes developers away from their core work. And now, with AI-generated code introducing vulnerabilities at greater speed and volume than ever before, remediation is taking even more time.

Continuous vulnerability management is not just a best practice—it's a necessity. With so many open-source dependencies to choose from (almost 3 million on the npm registry!), it’s no wonder supply chain security incidents are the focus of malicious actors. Let’s not forget the rise of ChatGPT, LLM chatbots, and AI-assisted code generation.

Authentication is the process that verifies the user's identity to control access to resources, prevent unauthorized users from gaining access to the system, and record user activities (to hold them accountable for their activities). It is used to authenticate users who log on to a server, ensure that software comes from a reputable source, and ensure that the person sending the message is who he says he is.

In cybersecurity, transparency matters—because none of us are immune. Increasingly, we’re seeing threat actors hone in on specific organizations. When we detected the recent “Contagious Interview” campaign targeting one of our own, our team acted fast to stop it in its tracks. We’re sharing this story so others can see how easily these attacks unfold—and how quickly they need to be stopped to protect the community.

This post is based on ongoing security research – and will continue to be updated as we get additional information…