
What Is a Zero Day? Definition, Examples, and How to Protect Yourself
A zero day is a software flaw that is unknown to the vendor and has no patch or fix available yet. Attackers can exploit it before anyone has had a chance to defend against it, which is why zero-day attacks are among the most feared threats in cybersecurity. In this guide, you will learn what is a zero day, how zero-day vulnerabilities, exploits, and attacks differ, how an attack unfolds, real-world examples, and the practical steps that protect you and your organization.
What Is a Zero Day?
A zero day, also written zero-day, is a security flaw in software, hardware, or firmware that the developer does not know about yet. The name comes from the time the vendor has had to fix it: zero days. Because there is no patch, there is no official defense, and security tools that rely on known signatures may not recognize the attack.
Every piece of software contains bugs. Most are harmless. A small number create a security weakness, such as a way to run code, bypass authentication, or read data that should be protected. When that weakness is discovered by an attacker first, or is kept secret instead of being reported, it becomes a zero day.
It is important to be precise about three related terms, because they are often used interchangeably.
Zero-Day Vulnerability, Exploit, and Attack
A zero-day vulnerability is the flaw itself. It is a weakness in code, such as a buffer overflow, a logic error, or an unsafe way of handling input. A vulnerability on its own does not cause harm until someone uses it.
A zero-day exploit is the code or technique that takes advantage of that flaw. It is the weapon built to trigger the vulnerability and gain an outcome the attacker wants, such as remote code execution, privilege escalation, or data theft.
A zero-day attack is the actual use of that exploit against a real target. An attack may be a single incident or a campaign that hits many organizations before the flaw is disclosed and patched.
So the chain is simple: a vulnerability is the hole, an exploit is the tool that uses the hole, and an attack is the event in which the tool is used.
How a Zero-Day Attack Works
Zero-day attacks follow a predictable lifecycle, even though the details change with each flaw.
1. Discovery
Someone finds the flaw. That person may be a security researcher, a bug-bounty hunter, a criminal group, or a state-sponsored team. Researchers often use code review, fuzzing, and reverse engineering to find weaknesses in browsers, operating systems, email servers, and widely used libraries.
2. Weaponization
The discoverer, or someone they sell the flaw to, builds a reliable exploit. This step turns a crash or a theoretical weakness into code that works consistently on a target system, often without the user noticing anything.
3. Delivery and Exploitation
The exploit is delivered, usually by a phishing email, a malicious website, a poisoned document, or a direct connection to an exposed server. When the victim opens the file, visits the page, or the server processes the crafted request, the exploit runs and gives the attacker a foothold.
4. Persistence and Lateral Movement
Once inside, the attacker installs malware, steals credentials, escalates privileges, and moves to other systems. The goal is rarely the first computer. It is the data, the domain controller, the email system, or the backup server.
5. Disclosure and Patching
Eventually the flaw is found by a defender, reported to the vendor, or discovered after an incident. The vendor develops a patch, and the clock changes. From that point, the flaw is no longer a zero day. It becomes a known vulnerability, and anyone who delays patching is at risk from the many attackers who can now copy the exploit.
The most dangerous period is the window between exploitation and patching. That window can last hours, weeks, or in some cases months, and defenders have no signature or patch to rely on during it.
Zero-Day vs. Known Vulnerability vs. N-Day
| Feature | Zero-Day Vulnerability | Known Vulnerability | N-Day Vulnerability |
|---|---|---|---|
| Vendor awareness | Unknown to the vendor | Known and usually disclosed | Known for N days |
| Patch available | No | Yes, in most cases | Yes |
| Detection | Very hard; no signature yet | Possible with scanners and signatures | Possible, if patched or monitored |
| Risk | Very high | High if unpatched, lower if patched | High when patching is delayed |
| Best defense | Layered defenses and fast response | Patching and scanning | Patching on schedule |
An N-day vulnerability is a known flaw that is N days old. The name sounds less alarming, but N-day flaws cause far more breaches in practice, because organizations leave known patches unapplied for months. Zero days get the headlines. Unpatched known flaws do most of the damage.
Types of Zero-Day Attacks
Browser Zero Days
Flaws in Chrome, Firefox, Safari, and Edge are highly prized, because a single malicious web page can compromise a visitor. Attackers often chain a browser flaw with a sandbox escape to run code outside the browser.
Operating System Zero Days
Flaws in Windows, macOS, Linux, iOS, and Android can give an attacker control of the whole device. These are often used in targeted attacks against journalists, activists, and executives.
Server and Application Zero Days
Flaws in email servers, file-transfer tools, VPNs, and web applications can expose whole organizations at once. One vulnerable server can be the entry point for ransomware across a network.
Library and Supply-Chain Zero Days
Some of the worst zero days live in a shared library used by thousands of products. When that library is flawed, every product that includes it is at risk, and patching requires coordination across many vendors.
Real-World Zero-Day Examples
Stuxnet (2010)
Stuxnet used four zero-day vulnerabilities in Windows to spread and to target industrial control systems. It showed that a zero day could be used not just to steal data, but to physically damage equipment.
Microsoft Exchange ProxyLogon (2021)
In early 2021, attackers exploited zero-day flaws in Microsoft Exchange Server to gain access to email servers around the world. Many organizations were compromised before patches were released, and the incident forced emergency patching across the industry.
Log4Shell (2021)
Log4Shell, tracked as CVE-2021-44228, was a flaw in the widely used Apache Log4j logging library. An attacker could send a specially crafted string and gain remote code execution on a server. Because Log4j was embedded in countless applications, the flaw affected organizations in almost every sector.
MOVEit Transfer (2023)
In 2023, the Clop ransomware group exploited a zero-day SQL injection flaw in MOVEit Transfer, a managed file-transfer product. The attack exposed data from hundreds of organizations and millions of people, showing how one product flaw can become a mass-extortion event.
Pegasus Spyware
Pegasus, developed by NSO Group, has used zero-day flaws in iOS and Android, including zero-click exploits that required no action from the victim. A missed call or a silent message could be enough. These cases explain why zero days are so valuable to governments and brokers, and why they can sell for hundreds of thousands or millions of dollars.
Who Finds Zero Days, and Why?
Not everyone who finds a zero day has the same motive. Security researchers report flaws to vendors, often through bug-bounty programs, and are paid for responsible disclosure. Criminal groups keep flaws secret and use them for ransomware, data theft, and fraud. Brokers buy flaws and sell them to governments or other buyers. Nation-state teams use them for espionage and sabotage.
This market is part of the problem. A flaw reported responsibly gets fixed. A flaw sold on the black market may be used for months before anyone knows it exists. That is why disclosure policy, bug bounties, and coordinated vulnerability disclosure matter so much.
Why Zero Days Are So Dangerous
Zero days are dangerous for three reasons. First, there is no patch, so the normal fix does not exist. Second, antivirus and intrusion detection often rely on known patterns, and a new exploit may not match any of them. Third, a single flaw in a popular product can affect millions of users at once.
That does not mean you are helpless. It means defense cannot depend on one tool. You need layers that limit what an exploit can do even when it succeeds.
Best Practices to Protect Against Zero-Day Attacks
Patch Fast, and Patch Everything
Apply security updates as soon as they are tested and available, including the operating system, browsers, office software, VPNs, and firmware. Enable automatic updates on personal devices. For organizations, a clear patching window and an emergency patching process for critical flaws are essential. Vulnerability scanning helps you find the systems you missed.
Use Layered Defenses
No single control stops a zero day. Combine endpoint detection and response, a firewall, email filtering, web filtering, and application allowlisting. If one layer fails, the next layer can block the download, the command-and-control connection, or the lateral movement.
Apply Least Privilege and Segmentation
Give users and services only the access they need. Segment the network so a compromised workstation cannot reach a database or a backup server directly. Privilege escalation is far less useful when the account has little to escalate to.
Use Virtual Patching
When a vendor patch is not yet available, a web application firewall or intrusion prevention rule can block the exploit pattern. This is called virtual patching. It is not a replacement for the real patch, but it can buy time.
Back Up and Test Restores
Keep offline, tested backups. Ransomware groups often use zero days to gain entry and then encrypt data. A backup you can restore from turns a disaster into an incident.
Train People and Limit Risky Behavior
Many zero days still need a click, a download, or a visit to a malicious site. Phishing training, safe browsing habits, and blocking macros and untrusted attachments reduce the chance that an exploit ever reaches a vulnerable system.
Monitor Behavior, Not Just Signatures
Use tools that watch for unusual behavior, such as a browser spawning a shell, a new process connecting to an unknown server, or a user account accessing systems it never touches. Behavioral detection is one of the best defenses against an exploit no one has seen before.
Common Mistakes to Avoid
First, do not assume antivirus alone will save you. Signature-based tools are useful, but they are weakest against brand-new exploits. Second, do not delay patches because a system is working fine. That is exactly when a known flaw becomes an easy target. Third, do not expose management interfaces, email servers, and file-transfer tools directly to the internet without strong authentication and monitoring. Fourth, do not ignore a vendor security advisory because it does not name your product. Shared libraries mean a flaw can affect products you did not expect. Finally, do not treat a zero-day headline as a reason to panic, and do not treat the absence of headlines as a reason to relax. The most common breaches still start with phishing, weak passwords, and unpatched known flaws. Kerberoasting is a good example of a well-known attack technique that still succeeds when credentials and Active Directory are not hardened.
What to Do When a Zero Day Is Announced
Check whether you use the affected product and version. Apply the vendor patch or mitigation immediately, and prioritize internet-facing systems. Look for indicators of compromise the vendor publishes, check logs for exploitation attempts, and reset credentials if there is evidence of access. Communicate clearly to staff and customers, and do not wait for a perfect fix when a workaround can reduce risk now.
Frequently Asked Questions
What is a zero day in simple terms?
A zero day is a software flaw that the vendor does not know about yet, so there is no patch for it. Attackers can use it before defenders have a fix.
Why is it called a zero day?
It is called a zero day because the vendor has had zero days to fix the flaw since it was discovered. Once the vendor learns about it and releases a patch, it is no longer a zero day.
What is a zero-day exploit?
A zero-day exploit is code or a technique that takes advantage of an unknown flaw. It turns the vulnerability into a working attack, such as running malicious code on a victim’s computer.
Can antivirus stop a zero-day attack?
Antivirus can sometimes stop a zero-day attack, especially if it uses behavioral detection, but it cannot be relied on alone. New exploits may not match any known signature, so layered defenses, patching, and behavioral monitoring are also needed.
How can I protect myself from zero-day attacks?
Keep all software updated, use strong, unique passwords and multi-factor authentication, use reputable security software, avoid suspicious links and attachments, back up your data, and limit the permissions of apps and accounts.
Conclusion
A zero day is a flaw with no patch and no warning. You cannot prevent every zero day, and you cannot patch what no one knows about. You can, however, make an exploit far less useful by patching quickly, layering defenses, limiting privileges, monitoring behavior, and keeping tested backups. That is the real lesson of every major zero-day incident: the organizations that recover fastest are not the ones with perfect software. They are the ones that were prepared for the flaw they had not seen yet.


