Skip to content
BENIBIX Learn

Zero-Day Vulnerability

Development🔐 SecuritySecurity Basics

Also known as Zero-Day, 0-Day, Zero-Day Exploit, Zero-Day Attack

A hole that bad people find before the maker does. There is no fix yet.

Think of it like

Think of it like a hole in a fence that the owner has not seen. A thief finds it first.

Example

Attackers find a flaw in a popular browser and use it quietly for weeks. The maker hears of it and ships an update two days later.

Why it matters

No patch can save you from a zero-day. Layers like least privilege and quick updates limit the damage.

Definition

A zero-day is a security hole that attackers know about before the maker does. The name means the maker has had zero days to fix it. There is no patch yet, so everyone using the software is open to attack. Once the maker learns of it, they race to ship a fix. After the fix is out, it is no longer a zero-day.
The lit-up box is the zero-day. Attackers have an exploit, and the maker has no fix.

Common mistake

Calling every new bug a zero-day. Once a fix is out, it is a known flaw, and not updating is the real problem.

Key takeaways

  1. 1
    Attackers know first. The maker does not know yet.
  2. 2
    No patch yet. Updates cannot help until one ships.
  3. 3
    A short life. It ends when the fix is out.