Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
A zero-day is a vulnerability that has no fixed version yet. Japan's Ministry of Internal Affairs and Communications (MIC) describes a zero-day attack as one that uses a vulnerability after it is discovered and before the maker distributes a fix. The NIST glossary also uses the same name for an attack that exploits a vulnerability not previously known.
How does a zero-day work?
Imagine a flaw found in a new type of lock. Before the maker issues a corrected product, a thief who knows of the flaw starts going around to houses with that lock. The owner would like to take the usual step of changing the lock, but no replacement exists in the world yet. A zero-day is that state.
With an ordinary vulnerability, the maker releases a fixed version and the hole closes when the user updates. With a zero-day, that fixed version does not exist. MIC says a fix often takes time to develop and that a complete countermeasure is hard.
The time between the discovery of a hole and the distribution of a fix is the period zero-day attacks aim at. Updating cannot deal with it, so what matters is how you get through to the day you can update. For what late updates lead to, see unpatched software.
Why do zero-days matter?
Because during this period the premise that you are safe if you update does not hold. In IPA's Top 10 Information Security Threats 2026, attacks that exploit system vulnerabilities rank fourth for organizations. That item is not limited to zero-days, but it shows that attacks on vulnerabilities are a leading threat.
There are things a site operator can do before a fixed version appears. First, apply any workaround the maker publishes, at once. Next, stop unused features and plugins, and narrow the places from which the admin screen can be reached. Virtual patching, which stops dangerous traffic at the entrance, can also buy time.
In parallel, get to a state where you can recover even if damage occurs. Check that backups are being taken and that you have tried the restore steps. When the fixed version is out, update without delay. Our Cyber Shield Guard Pro has virtual patching and notification of serious detections within 15 minutes.
What should you do while waiting for a fix?
- Apply the maker's workaround if there is one.
- Stop unused features and plugins, and narrow access to the admin screen.
- Consider virtual patching as a stopgap.
- Check backups and the restore steps.
- Update the day a fixed version is out.
For help with this, contact us.
Related terms
- Virtual patching: a stopgap that blocks only the traffic aimed at a known hole until the fixed version is out
- Vulnerability: a security hole in a program or its settings
Frequently asked questions
Can users defend against a zero-day?
Not completely. The Ministry of Internal Affairs and Communications also says that a fix often takes time to develop, so a complete countermeasure is hard. Layer the official workaround, stopping unused features, a mechanism that stops traffic at the entrance, and checked backups to make damage less likely.
How is a zero-day different from an ordinary vulnerability?
The difference is whether a fixed version exists. An ordinary vulnerability is closed by updating. A zero-day is the period before an update is ready, so the question is how to protect yourself while you wait. When a fixed version appears, update at once.
Where can I learn about zero-days?
The official advisory of the product you use comes first. For products in Japan they also appear on JVN, the vulnerability information site run by JPCERT/CC and IPA. For WordPress plugins, watch the update notices in the admin screen and the maker's announcement page.
Next step
The free URL check shows only what is visible from outside. To decide how to protect yourself while a fix is awaited, contact us and tell us your situation. Late updates are covered in unpatched software.
Frequently asked questions
Can users defend against a zero-day?
Not completely. The Ministry of Internal Affairs and Communications also says that a fix often takes time to develop, so a complete countermeasure is hard. Layer the official workaround, stopping unused features, a mechanism that stops traffic at the entrance, and checked backups to make damage less likely.
How is a zero-day different from an ordinary vulnerability?
The difference is whether a fixed version exists. An ordinary vulnerability is closed by updating. A zero-day is the period before an update is ready, so the question is how to protect yourself while you wait. When a fixed version appears, update at once.
Where can I learn about zero-days?
The official advisory of the product you use comes first. For products in Japan they also appear on JVN, the vulnerability information site run by JPCERT/CC and IPA. For WordPress plugins, watch the update notices in the admin screen and the maker's announcement page.