Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is an N-Day Attack?

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.

Illustration for the cybersecurity term N-Day Attack
Home / Blog / Cybersecurity Terms / What Is an N-Day Attack?
17 November 2026

What Is an N-Day Attack?

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.

The Window Opens When the Patch Ships

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.

Why Defenders Stay Behind

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.

Who Uses N-Days

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.

Closing the Window

The honest objective is not patching everything immediately; it is patching the right things fast enough.

  1. Work from exploitation, not just severity. The CISA Known Exploited Vulnerabilities catalogue lists flaws confirmed to be exploited in the wild, and the EPSS score estimates the probability that a given CVE will be. Together they are a far better queue than CVSS alone, which has no concept of whether anyone is actually attacking it.
  2. Tier your estate by exposure. Internet-facing VPN concentrators, file transfer systems, and mail servers need an emergency path measured in hours. Internal workstations can follow the normal cycle.
  3. Keep the inventory current. You cannot patch an appliance you forgot about, and attack surface discovery regularly finds services no one on the IT team recognises.
  4. Have compensating controls ready. Virtual patching at the WAF, egress filtering from server networks, and temporary access restrictions buy time when a patch is unavailable or risky.
  5. Hunt as well as patch. For anything exploited before you fixed it, assume compromise and look for the evidence. A patch does not remove a web shell.

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.

FAQ – Frequently Asked Questions

Is an N-Day More or Less Dangerous Than a Zero-Day?

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.

How Fast Does a Proof-of-Concept Usually Appear?

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.

Should We Prioritise by CVSS Score?

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.

What Should We Do If We Cannot Patch in Time?

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.

Related Terms

You May Be Interested In These

What Is TISAX?

Cybersecurity Terms

17 November 2026

What Is TISAX?

Read More
What Is Alert Fatigue?

Cybersecurity Terms

17 November 2026

What Is Alert Fatigue?

Read More
How Do You Choose a Cryptographic Library?

Cybersecurity Terms

17 November 2026

How Do You Choose a Cryptographic Library?

Read More