Zero-Day Vulnerability
Subject: Computer and Technology noun /ˈzɪr.oʊˌdeɪ ˌvʌl.nər.əˈbɪl.ə.ti/ 1 definition
- information-security
- software-security
- vulnerability-management
- threat-intelligence
-
Definition (noun)
Entry #185 · UpdatedA Zero-Day Vulnerability (often written as 0-day) is a security flaw in software, firmware, or hardware that is unknown to the vendor or publicly disclosed before an official patch is available, giving defenders zero days of advance warning to remediate it. Because no vendor-supplied fix exists yet, signature-based defenses often fail to detect exploitation attempts until the flaw is discovered and analyzed. The term refers strictly to the underlying unpatched weakness, distinguishing it from a zero-day exploit (the code or technique crafted to abuse the flaw) and a zero-day attack (active exploitation against live targets).
Common Forms
In-the-Wild Zero-Days: Undisclosed flaws actively exploited against production systems before the vendor knows about the bug or distributes a security update.
Publicly Disclosed Zero-Days: Vulnerabilities revealed openly—sometimes alongside proof-of-concept code—before an official fix exists, leaving defenders reliant on temporary mitigations.
Privately Held Zero-Days: Unpatched flaws discovered through independent research and retained by exploit brokers, intelligence programs, or threat groups rather than reported to the vendor.
Third-Party Component Zero-Days: Newly uncovered flaws inside shared libraries, drivers, or embedded firmware that expose downstream products until upstream maintainers and integrators ship patches.
Example
Security analysts inspecting firewall logs detect unexpected outbound reverse shells originating from an enterprise VPN appliance running the vendor's latest firmware release. Investigation uncovers an unauthenticated command-injection bug in the web management interface that is unknown to the vendor, forcing the operations team to isolate the gateway until an emergency hotfix is issued.