A zero-day attack is a cyberattack that exploits a previously unknown security vulnerability, often before a vendor can release a patch. The flaw may affect software, hardware, or firmware. Attackers can exploit it to steal data, run malicious code, or gain unauthorized access while defenders have little warning.
The term “zero-day” reflects the lack of advance time to fix a vulnerability before exploitation begins. Because protective signatures and patches may be unavailable, stopping these attacks requires more than conventional defenses.
Zero-Day Attack vs. Exploit vs. Vulnerability
| Comparison | Meaning | Example |
|---|---|---|
| Zero-Day Vulnerability | A previously unknown security flaw exploited before an effective fix is available, often before public disclosure. | An undisclosed flaw in a web application. |
| Zero-Day Exploit | The code or technique used to exploit the vulnerability. | A crafted request that triggers the vulnerability. |
| Zero-Day Attack | An actual attempt to compromise a system using the exploit. | An attacker uses the exploit to gain unauthorized access to the application. |
How Do Zero-Day Attacks Work?
- Vulnerability discovery: An attacker discovers or obtains information about an undisclosed vulnerability in an application, operating system, or network component.
- Exploit development: The attacker develops a method to take advantage of the vulnerability and gain unauthorized access or execute malicious actions.
- Attack execution: The attacker delivers the exploit through channels such as malicious files, compromised websites, or manipulated network requests.
- System compromise: Once successful, the attack may enable data theft, malware installation, privilege escalation, or unauthorized system control.
- Vulnerability disclosure and patching: The vulnerability is eventually discovered, and the vendor releases a patch or mitigation to address it.
Why Are Zero-Day Attacks Dangerous?
The greatest risk is the gap between exploitation and effective defense. During that period:
- Defenders may lack a fix. Even organizations with strong patch-management programs cannot install a patch that does not yet exist.
- Attack activity may be difficult to recognize. Detection rules for the specific exploit may be unavailable, and apparently legitimate requests can trigger unexpected behavior.
- A single flaw can expose critical systems. Internet-facing applications and widely deployed enterprise products can give attackers an entry point into sensitive environments.
The consequences depend on the vulnerability and the access it provides. Some attacks cause service disruption; others enable persistent access or large-scale data theft.
How to Detect Zero-Day Attacks
Anomaly Detection Using Statistical Analysis
Statistical anomaly detection establishes baselines of normal network and system activity, and identifies unusual deviations. Unexpected traffic spikes, abnormal request frequencies, or unusual resource consumption may indicate potential exploitation, allowing security teams to investigate threats that have not been previously identified.
Known Threat Detection Through Signature-Based Analysis
Signature-based detection compares incoming traffic, files, and system activities against databases of known attack patterns. When a match is found, security tools can flag or block the threat. However, this approach has limitations when detecting zero-day attacks because their signatures may not yet be available.
Identifying Unusual Activities Through Behavior-Based Detection
Behavior-based detection monitors application, user, and system activities to identify deviations from normal behavior. Unusual access attempts, unexpected application processes, and abnormal API requests may indicate malicious activity, helping security teams identify potential zero-day attacks without relying solely on known threat signatures.
How to Mitigate Zero-Day Attacks
Although organizations cannot eliminate every zero-day vulnerability, several security measures can reduce their exposure and limit the impact of successful exploitation.
Apply Security Patches and Software Updates
Regularly updating operating systems, applications, frameworks, and third-party components helps address known vulnerabilities. Organizations should establish a patch management process to prioritize critical security updates and minimize the time between vulnerability disclosure and remediation. Organizations should also monitor security advisories and apply emergency patches as soon as they become available.
Deploy a Web Application Firewall (WAF)
A WAF inspects and filters HTTP/HTTPS traffic to detect and block malicious requests and exploitation attempts targeting web applications. Through virtual patching, WAF rules can help block traffic targeting known vulnerabilities while organizations wait for official security patches.
Implement an Intrusion Prevention System (IPS)
An IPS monitors network traffic for suspicious activities and automatically blocks detected threats based on configured security policies. Combined with other security controls, an IPS can help prevent unauthorized access and limit the impact of exploitation attempts.
How CDNetworks Helps Protect Against Zero-Day Attacks
CDNetworks Web Application Firewall (WAF) helps organizations defend against zero-day exploitation through AI-powered detection, automated rule updates, and global threat intelligence. Its key capabilities include:
- AI-Powered Detection: Analyzes traffic patterns using AI/ML to identify abnormal behavior and emerging exploitation techniques that traditional signature-based rules may miss.
- Automated Zero-Day Protection: Deploys emergency rule patches globally when new vulnerabilities emerge, helping protect applications without waiting for manual rule updates.
- Global Threat Intelligence: Leverages continuously updated threat intelligence to identify and block malicious IPs, known attackers, and common exploit patterns before they reach applications.
Operating across 3,000+ global PoPs, CDNetworks WAF inspects and filters HTTP/HTTPS traffic at the edge, helping organizations reduce exposure to zero-day exploits while maintaining application availability and performance.
FAQ
Why is it called a zero-day attack?
The term “zero-day” refers to the fact that software developers have had zero days to fix a vulnerability before it is exploited. In many cases, the vulnerability is unknown to the software vendor when attackers discover and exploit it, leaving no time to develop and release an official security patch.
Is every unpatched vulnerability a zero-day?
No. A publicly known vulnerability can remain unpatched for months. “Zero-day” describes exploitation before defenders have meaningful advance knowledge or a timely fix, not simply the absence of a patch.
What is an example of a zero-day attack?
The 2023 MOVEit Transfer attack is a well-documented example. Attackers exploited a previously unknown SQL injection vulnerability (CVE-2023-34362) before public disclosure, enabling data theft from affected organizations.
A more recent case is PHP2Shell (2026), involving two critical vulnerabilities in the PHP runtime. Following disclosure, exploitation was confirmed against exposed PAN-OS management interfaces. CDNetworks also released a dedicated WAF rule to help mitigate associated malicious requests.