Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Zero-Day Vulnerability?

A zero-day vulnerability is a security flaw that the software vendor does not yet know about or has not yet fixed, leaving defenders with no patch when attackers begin to exploit it.

Illustration for the cybersecurity term Zero-Day Vulnerability
Home / Blog / Cybersecurity Terms / What Is a Zero-Day Vulnerability?
17 November 2026

What Is a Zero-Day Vulnerability?

What Is a Zero-Day Vulnerability?

A zero-day vulnerability is a security flaw that is unknown to the vendor, or known but not yet fixed, at the moment attackers start exploiting it. The name refers to the number of days the vendor has had to address the problem: zero. An attack that uses such a flaw is called a zero-day attack, and the code used is a zero-day exploit.

Zero-days are particularly dangerous because the usual first line of defence, applying a patch, is not available. Signature-based security tools may not recognise the attack either, since it has never been seen before.

Zero-Day, N-Day, and the Patch Gap

Once a vulnerability is publicly disclosed and a patch is released, it is no longer a zero-day. It becomes what is sometimes called an n-day vulnerability. In practice, n-days cause far more breaches than zero-days, because many organisations take weeks or months to patch. Attackers often reverse-engineer patches to create exploits within days, so the period immediately after a patch release can be the most dangerous of all for organisations that are slow to update.

Who Uses Zero-Days

Zero-day exploits are expensive to discover and develop, so they are used selectively:

Google’s threat intelligence and Project Zero teams track zero-days exploited in the wild and have reported dozens each year, with a growing share targeting enterprise security and networking products such as VPN gateways and firewalls.

The Zero-Day Lifecycle

  1. Discovery: a researcher, vendor, or attacker finds the flaw.
  2. Exploitation: if an attacker finds it first, they may exploit it quietly for months.
  3. Detection: defenders, researchers, or the vendor notice the exploitation or the flaw.
  4. Disclosure: the vulnerability is reported to the vendor and, eventually, made public, often with a CVE identifier.
  5. Patch release: the vendor issues a fix, sometimes as an emergency out-of-band update.
  6. Patch adoption: organisations deploy the fix, which can take a long time.

Responsible disclosure and bug bounty programmes encourage researchers to report flaws to vendors rather than sell them.

Defending Against Zero-Days

You cannot patch a vulnerability that has no fix, but you can make exploitation harder and limit the damage through defence in depth:

Zero-Days and Vulnerability Management

Zero-days attract headlines, but most organisations face far greater risk from known vulnerabilities left unpatched. A mature vulnerability management programme, with accurate asset inventories and fast patching, is also the foundation of a quick response when a zero-day affecting your environment is announced.

At Privia Security, our Penetration Test Services assess how well your layered defences would contain an attacker who arrives with an exploit you cannot yet patch.

FAQ – Frequently Asked Questions

Can Antivirus Software Stop Zero-Day Attacks?

Traditional signature-based antivirus struggles against zero-days because the attack has not been seen before. Modern endpoint detection and response tools perform better, as they look for suspicious behaviour, such as unusual process activity or memory manipulation, rather than known signatures. Even so, layered defences, least privilege, and segmentation remain essential to limit any damage.

What Is the Difference Between a Zero-Day and an N-Day Vulnerability?

A zero-day is unknown to the vendor or has no available patch when it is exploited. An n-day is a vulnerability that has already been disclosed and patched, but remains exploitable on systems that have not been updated. N-days account for most real-world breaches, which is why fast patching matters so much.

How Should I Respond When a Zero-Day Is Announced?

Check quickly whether you use the affected product and version, apply any vendor mitigations or workarounds immediately, and patch as soon as a fix is released. Look for signs of exploitation using published indicators, especially if the system is internet-facing, and consider isolating exposed systems until they are protected. NCSC alerts provide useful guidance.

Related Terms

You May Be Interested In These

What Is Crypto Agility?

Cybersecurity Terms

17 November 2026

What Is Crypto Agility?

Read More
What Is Biometric Authentication?

Cybersecurity Terms

17 November 2026

What Is Biometric Authentication?

Read More
What Is the GoAnywhere MFT Vulnerability?

Cybersecurity Terms

17 November 2026

What Is the GoAnywhere MFT Vulnerability?

Read More