A zero-day vulnerability is a software flaw unknown to the vendor, with no patch available, that attackers can exploit before a fix exists. The vendor has had zero days to fix it, so the usual defence of patching does not work in the exposure window. Defence relies on defence in depth, network segmentation, application control, behaviour-based detection, and rapid patching once a fix is released. The Essential Eight reduces zero-day impact even though it cannot prevent an unknown flaw.
Most cyber attacks exploit known vulnerabilities that have patches available but have not been applied. Zero-days are the harder problem: vulnerabilities that no one has fixed yet, because no one on the defending side knows they exist.
What makes a zero-day different from a known vulnerability?
A zero-day vulnerability is a security flaw in software that is unknown to the party responsible for fixing it, typically the software vendor, and for which no patch exists. The term “zero-day” refers to the number of days the vendor has had to address the flaw: zero. From the moment the vulnerability is discovered by an attacker to the moment the vendor learns of it and releases a fix, the flaw can be exploited against affected systems with little to stop it.
This is what makes zero-days distinct from the far more common known vulnerabilities. A known vulnerability has been disclosed, has been assigned an identifier (a CVE), usually has a severity score, and typically has a patch available. The defence against a known vulnerability is to apply the patch. A zero-day has none of these: no disclosure, no patch, and often no detection signature.
What is the difference between a zero-day vulnerability, exploit and attack?
Three related terms are often used loosely but mean different things.
A zero-day vulnerability is the flaw itself, the weakness in the software that could be taken advantage of.
A zero-day exploit is the specific method or piece of code that takes advantage of the vulnerability to achieve an effect, such as executing arbitrary code or bypassing authentication.
A zero-day attack is the actual use of the exploit against a target while the vulnerability is still unpatched.
Once the vendor becomes aware and releases a patch, the vulnerability is no longer strictly a zero-day. But systems that have not yet applied the patch remain exposed, and these are sometimes called “n-day” vulnerabilities, exploited in the window between patch release and patch application. In practice, many damaging attacks use n-day vulnerabilities: the patch existed, but the organisation had not applied it yet.
Why are zero-day vulnerabilities so dangerous?
The danger of a zero-day comes from the absence of the usual defences during the exposure window.
There is no patch to apply, so the primary defence against vulnerabilities does not exist. Signature-based security tools, which detect known threats by matching against a database, may not recognise a novel exploit. Even fully updated, well-maintained systems can be compromised, because being up to date does not help against a vulnerability that has no fix.
The exposure window can be long. A zero-day may be discovered and exploited by a sophisticated actor months before it is detected and disclosed. During that time, the actor can operate against high-value targets with a high success rate and little risk of detection.
High-value zero-days, particularly in widely deployed software, operating systems, browsers, VPN products and internet-facing enterprise systems, are extremely valuable. They are traded in criminal markets and by exploit brokers for large sums, and are used by well-resourced actors including nation-state groups, who may hoard them for espionage rather than disclose them.
How can organisations defend against zero-day attacks?
Because a zero-day cannot be patched before a fix exists, defence shifts from prevention of the specific vulnerability to reducing exposure, containing impact, and detecting exploitation.
Defence in depth. No single control should be the only thing standing between an attacker and a critical asset. Layered controls mean that exploiting one vulnerability does not lead directly to full compromise. An attacker who exploits a zero-day in a web server should still face segmentation, access controls, monitoring and further authentication before reaching sensitive data.
Network segmentation. Segmentation limits how far an attacker who exploits a zero-day can move. Containing a breach to one segment buys time and limits damage.
Application control. Allowing only approved applications to execute means that even if a vulnerability is exploited to attempt to run malicious code, that code may be blocked. Application control is one of the Essential Eight mitigations and is effective against many post-exploitation actions.
Behaviour-based detection. Endpoint detection and response (EDR) tools that detect anomalous behaviour, rather than only known signatures, can identify exploitation activity even when the specific exploit is novel. Unusual process behaviour, unexpected network connections, and privilege escalation attempts are detectable regardless of the specific vulnerability used.
Reducing attack surface. Every internet-facing service is a potential zero-day target. Reducing attack surface by disabling unnecessary services, minimising internet-facing systems, and removing unused software reduces the number of places a zero-day could strike.
Rapid patching once a fix exists. The moment a vendor releases a patch, the race is on. Organisations that patch internet-facing systems fast close the n-day window before opportunistic attackers exploit it. The Essential Eight requires patching internet-facing services within 48 hours of a critical patch release for this reason.
Threat intelligence and vendor advisories. Monitoring ASD alerts, vendor security advisories and threat intelligence feeds gives early warning of actively exploited vulnerabilities, allowing organisations to apply mitigations, tighten monitoring, or take affected systems offline before a patch is available.
How do Australian frameworks address zero-day risk?
The ASD’s ACSC issues alerts and advisories when significant vulnerabilities, including actively exploited zero-days, affect software used by Australian organisations. These advisories often include interim mitigations to apply before a patch is available. Organisations should subscribe to and act on these promptly.
The Essential Eight mitigations collectively reduce zero-day risk. While they cannot prevent an unknown vulnerability, application control limits what exploited code can do, patch management closes the window rapidly once a fix exists, and restricting administrative privileges limits the impact of successful exploitation. The ASD Information Security Manual emphasises defence in depth, segmentation and rapid vulnerability response as the practical approach to unknown threats.
Regular penetration testing helps by finding and remediating known vulnerabilities before they are exploited, shrinking the pool of exploitable weaknesses and validating that defence-in-depth controls work as intended. Cybernion provides penetration testing and security advisory services to help organisations build resilience against both known and unknown threats.
Frequently asked questions
What is a zero-day vulnerability?
A zero-day vulnerability is a software security flaw that is unknown to the vendor and for which no patch or fix yet exists. The name refers to the vendor having had zero days to address it. Because there is no patch, a zero-day exploit can be used against affected systems with a high success rate until the vendor becomes aware, develops a fix, and organisations apply it. Zero-days are valuable to attackers precisely because defences that rely on known signatures or available patches cannot address them.
What is the difference between a zero-day vulnerability, exploit and attack?
A zero-day vulnerability is the underlying flaw in the software. A zero-day exploit is the specific technique or code that takes advantage of the vulnerability. A zero-day attack is the act of using that exploit against a target before a patch is available. The vulnerability is the weakness, the exploit is the tool, and the attack is the use. Once a patch is released, the vulnerability is no longer technically a zero-day, though unpatched systems remain exposed until they are updated.
Why are zero-day vulnerabilities so dangerous?
Zero-days are dangerous because there is no patch available when they are first exploited, so the normal defence of applying updates does not work. Signature-based tools may not detect a novel exploit. Attackers can operate with a high success rate against fully updated systems during the window between first exploitation and a fix being available and applied. High-value zero-days, particularly in widely used software or internet-facing systems, are sold for large sums and used by sophisticated actors including nation states. The window of exposure can last from days to months.
How can organisations defend against zero-day attacks?
Since patching is not possible before a fix exists, defence relies on reducing exposure and detecting anomalous behaviour. Defence in depth ensures that a single exploited vulnerability does not lead to full compromise. Network segmentation limits lateral movement. Application control prevents unauthorised code from executing even if a vulnerability is exploited. Behaviour-based detection can identify exploitation activity that signature-based tools miss. Reducing attack surface by disabling unnecessary services limits the number of exploitable targets. Rapid patching once a fix is released closes the window quickly.
How do Australian frameworks address zero-day risk?
The Essential Eight mitigations reduce zero-day risk even though they cannot prevent an unknown vulnerability. Application control stops unauthorised code from running, patch management closes the window fast once a fix exists, and restricting administrative privileges limits the impact of exploitation. The ASD Information Security Manual emphasises defence in depth, network segmentation, and rapid patching. The ASD also issues alerts and advisories when significant vulnerabilities, including actively exploited zero-days, affect systems used by Australian organisations, and organisations should monitor and act on these promptly.
Sources:
- Information Security Manual, Australian Signals Directorate, 2026
- Essential Eight, Australian Signals Directorate, 2026
- Alerts and advisories, Australian Signals Directorate, 2026
Last updated: 30 August, 2026
