Sovra Recon·Glossary · Zero-day

Zero-day Vulnerability: Definition and How to Protect Against It

By Solan Barlet, co-founder of Sovra Recon
Updated October 29, 2026

In short

A zero-day (or 0-day) vulnerability is one exploited by attackers before the vendor is aware of it or has released a patch: defenders have had “zero days” to respond. Once the patch is released, it becomes an “n-day” vulnerability, often exploited on a massive scale on unpatched systems. In practice, the majority of compromises stem from known, unpatched vulnerabilities, not zero-days.

The Lifecycle of a Vulnerability

  • Discovery: by a researcher, the vendor, or an attacker.
  • Zero-day: exploited without a patch available.
  • Disclosure and patch: the vendor issues an advisory and an update, and a CVE is assigned.
  • N-day: Attackers analyze the patch and mass-exploit unpatched systems, often within a few days.

Protecting Yourself When There Is No Patch

  • Reduce the attack surface: what is not accessible from the Internet cannot be attacked from the Internet.
  • Defense in depth: network segmentation, least privilege, and MFA, so that a single vulnerability is not enough to compromise the entire system.
  • Detection: logs and EDR to identify abnormal behavior.
  • Apply the workarounds published by the vendor immediately, followed by the patch.

Frequently asked questions

Can a penetration test uncover a zero-day?

In your own application, yes: a previously unknown vulnerability in your code is, by definition, a zero-day. For third-party products, that is not the objective of a penetration test.

Sources

Find out where an attacker would get in.

Our AI agents actually attack your scope, fully automated, and hand you the proof of every vulnerability.