Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
An n-day attack exploits a vulnerability that has already been disclosed and patched, targeting the window between a vendor’s fix and the moment every affected system actually receives it.

What Is an N-Day Attack?
An n-day attack exploits a vulnerability that is already public and already fixed. The n stands for the number of days since disclosure, in contrast to a zero-day, where no patch exists at the moment of exploitation. It is the less glamorous half of offensive security and overwhelmingly the more common one. Most organisations are not compromised by a secret technique; they are compromised through something that appeared in a vendor advisory months earlier.
Publishing a fix is also publishing a specification of the bug. An attacker downloads the patched binary and the one before it, compares them with a tool such as BinDiff or Diaphora, and finds the changed function. A bounds check added here, a new input validation routine there—the modification points directly at the flaw. For interpreted languages and open source projects the work is easier still, because the commit message and the diff are published alongside the release.
This process, patch diffing, routinely produces a working exploit in a day or two. Proof-of-concept code then appears on GitHub, is folded into Metasploit or Nuclei templates within a week, and from that point requires no skill to use. Mass internet scanning for the vulnerable version follows immediately, which is why the first exploitation attempts against a freshly disclosed internet-facing flaw often arrive within hours.
Mandiant’s research on time-to-exploit has tracked this compression across successive years: the median interval between disclosure and observed exploitation has fallen sharply, and for internet-facing products it is now measured in days.
The gap is rarely caused by indifference. It is caused by the realities of operating software:
The result is a long tail. CVE-2017-0144, the SMB flaw behind EternalBlue and WannaCry, is still exploited successfully today. Older Microsoft Exchange chains remain productive years after disclosure. A vulnerability does not stop being useful because it is old; it stops being useful when the last unpatched instance disappears.
Nearly everyone. Ransomware affiliates prefer them because they are cheap and reliable, and because exploitation at scale finds victims who will pay. Initial access brokers scan for one specific vulnerable product and sell the footholds on. State-aligned groups use n-days for the majority of their operations and reserve genuine zero-days for targets where nothing else will work. Commodity botnets add new exploits to their modules within days of a proof of concept appearing.
The honest objective is not patching everything immediately; it is patching the right things fast enough.
Our Continuous Vulnerability Scanning Services track the disclosure-to-remediation interval across your external estate so that the window becomes a number you can manage rather than an assumption.
Individually a zero-day is more dangerous, because no defence exists. Collectively n-days cause far more damage, because they are available to everyone, exploited at internet scale, and used against organisations that had the fix available and did not apply it. A zero-day typically targets a handful of organisations; an n-day campaign can reach thousands within a week of a proof of concept appearing.
For widely deployed internet-facing software, often within one to three days of the patch. Researchers compare the patched and unpatched binaries to locate the changed code, which points directly at the flaw, and the resulting exploit is published for defensive testing. Automated scanning follows almost immediately, so the practical planning assumption should be that exploitation starts in the first week.
Not by CVSS alone. The score measures theoretical severity and takes no account of whether anyone is exploiting the flaw or whether the affected component is reachable in your environment. Combining CVSS with the CISA Known Exploited Vulnerabilities catalogue, EPSS probability, and your own exposure data produces a much shorter and far more useful remediation queue.
Reduce reachability and increase visibility. Restrict access to the affected service by source address, apply vendor-supplied mitigations or virtual patching rules, block the outbound connections an exploit would need, and raise monitoring on the host. Document the decision with an owner and a review date, so the temporary position does not quietly become permanent after the incident fades.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.