N-day exploit
An attack against a vulnerability that is already publicly known and already has a patch available. Most real-world server compromises use n-day exploits against servers that simply have not been patched yet, not zero-days.
Why this is the more common real-world risk
The overwhelming majority of successful attacks exploit vulnerabilities that were disclosed, and often patched, weeks, months or even years earlier. Attackers rely on the fact that many servers are slow to apply available patches.
The race that matters
Once a vulnerability and its patch become public, attackers frequently reverse-engineer a working exploit within days. The gap between a patch becoming available and it actually being applied is where most real damage happens.
Frequently asked questions
Is an n-day exploit less dangerous than a zero-day?
Not necessarily. Since the vulnerability is public and often well documented, exploit code can circulate quickly, making n-day attacks in some ways easier for attackers to execute at scale.
How fast should patches be applied to avoid this risk?
As close to immediately as your testing process allows, particularly for anything marked critical; delays measured in weeks are where most n-day attacks succeed.
Does automated patching solve this problem?
It significantly reduces the exposure window for most routine updates, though critical fixes sometimes still warrant manual, expedited review rather than waiting for the next scheduled unattended-upgrades run.
Want to see where your own server stands?
Run the free, read-only server check, or open the Security Lab and watch the detect, contain, recover, verify loop in action.
Get your free server checkOpen the Security Lab