Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Nuclei runs community-written YAML templates against targets at speed, turning a newly published vulnerability into a repeatable check within hours of disclosure.

What Is Nuclei?
Nuclei is a scanner built by ProjectDiscovery that works entirely from templates. Each template is a YAML file describing a request to send and the conditions that indicate a vulnerability: match this status code, find this string in the response, extract this value. The engine is written in Go and runs thousands of templates against many targets concurrently.
The design decision that made it significant is that the detection logic lives outside the tool. Anyone can write a template, and the community template repository holds several thousand of them, maintained publicly on GitHub. When a serious vulnerability is disclosed, a working template usually appears within hours, which means defenders can check their entire estate the same day without waiting for a vendor to ship a plugin.
A template declares an identifier, metadata including severity and the relevant CVE, the protocol to use, the request to send, and the matchers that decide whether the response indicates a problem. Matchers combine on status code, words, regular expressions, binary content, and response time, with logical operators between them. Extractors pull values out of responses for use in reporting or in a subsequent request.
Protocol coverage extends well beyond HTTP: DNS, raw TCP, file content, SSL and TLS configuration, WHOIS, WebSocket, and headless browser checks for issues that only appear after JavaScript executes. Workflows chain templates conditionally, so a technology fingerprint can trigger only the checks relevant to it, which is how large scans stay fast.
Templates are categorised by what they detect: CVEs, default credentials, exposed panels, misconfigurations, information disclosure, exposed files and tokens, and technology detection.
Before template-driven scanning, there was a useful gap between a vulnerability being disclosed and mass exploitation beginning, because attackers had to build their own detection and exploitation at scale.
That gap has largely closed. A template published within hours of disclosure can be pointed at a list of every host on the internet running the affected software, and the same capability is available to everyone. The practical consequence for defenders is that the window between a patch being published and internet-wide scanning for unpatched systems is now routinely less than a day. Exposed systems need to be patched on a timeline measured against that, not against a monthly change cycle. The dynamic is described more fully under n-day attacks.
The same capability is a defensive asset, and this is the part organisations underuse. Maintaining a target list of your own external estate and running Nuclei against it when a significant vulnerability drops answers the question everyone asks that morning, which is whether you are exposed, in minutes rather than days. It pairs naturally with attack surface monitoring.
Three cautions are worth stating plainly.
Templates are executable content from the internet. The standard library is reviewed, but templates found elsewhere are not. The code protocol allows a template to execute local commands and is disabled unless explicitly enabled with signed templates, which is the correct default. Review third-party templates before running them, exactly as you would an untrusted script.
Some templates are intrusive. Checks that confirm a vulnerability by exploiting it can alter data or crash a service. Review the severity and tags before running broad scans against production, and exclude fragile systems.
False positives occur. Template quality varies, and matchers written against one product version misfire on another. Validate significant findings manually before reporting them.
There is also a legal boundary that is easy to cross by accident. Running Nuclei against systems you do not own or have written authorisation to test engages the Computer Misuse Act 1990, and a scan is no less unauthorised for being automated or for having been pointed at a large list.
Nuclei is fast, current, and broad, and it is excellent at confirming known issues in known software. It does not replace an authenticated vulnerability scanner such as Nessus, which reads installed packages from inside the host rather than inferring exposure from outside. It does not replace an application scanner or a human, because it has no understanding of your application’s logic or authorisation model.
The sensible arrangement is layered: authenticated scanning for internal patch state, Nuclei for rapid external exposure checking and for same-day response to disclosures, and penetration testing for everything that requires judgement.
At Privia Security, our Continuous Vulnerability Scanning Services maintain an external target inventory and run template-based checks against it when significant vulnerabilities are published.
No. Nuclei checks what is observable from outside a host, which makes it fast and current but blind to software that exposes no network service. An authenticated scanner logs in and reads the installed package list, finding far more. Use authenticated scanning for internal patch state and Nuclei for rapid external exposure checking and same-day response to new disclosures.
The official repository is reviewed and widely used, which makes it reasonably trustworthy. Templates from elsewhere are executable content from the internet and should be read before use. The code protocol, which runs local commands, is disabled unless explicitly enabled with signed templates. Some legitimate templates are also intrusive enough to disrupt production services.
Frequently within hours for anything significant, and the community repository is public, so attackers and defenders get them at the same moment. This is why the window between a patch being published and internet-wide scanning for unpatched systems is now routinely less than a day for internet-facing software, rather than the weeks organisations often assume.
Yes, and it is one of the better uses of the tool. Keep a current inventory of your external hosts, and when a serious vulnerability is announced, run the relevant template against that list. You get an answer in minutes rather than waiting for the next scheduled scan. Ensure the inventory itself stays current, otherwise the answer is incomplete.
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.