by Robert Carney Nov 13, 2026
A new CVE (Common Vulnerabilities and Exposures) lands before your first meeting, along with a list of every device that runs an affected version. It might be a few hundred routers and firewalls, or a few thousand.
To complete a network CVE assessment and find out which of those devices are actually vulnerable, somebody has to read the vendor advisory, log in to each device, and check how it’s set up. A lot of that checking goes to devices that were never at risk, and those hours come from the engineers you would rather have designing your next network.
Security is waiting on the answer too. Leadership is asking where the company stands, and until someone checks the devices, security has nothing to tell them.
About 48,000 CVEs were published in 2025, setting a new record. The Forum of Incident Response and Security Teams (FIRST) expects close to 99,000 CVEs in 2026, and points to AI-assisted discovery as one of three drivers.
Attackers move just as fast. Industry research puts the time to turn a new flaw into a working attack at under five days, and some 2026 analyses say under 24 hours.
Network devices make this harder. Routers, firewalls and VPN gateways sit between the outside world and the rest of your network, so an attacker who gets into one can reach what’s behind it. These devices are also hard to fix: upgrades need reboots and maintenance windows, and many teams have no full test copy of production.
CISA (Cybersecurity and Infrastructure Security Agency) and its Five Eyes partners warned in February 2025 that attackers are targeting these network devices as a way into organizations. In February 2026, CISA ordered federal civilian agencies to replace edge devices that no longer get vendor patches. Endpoint detection tools often can’t run on these devices, so they lack the protection servers and laptops get.
A device is affected when its version matches the CVE. It’s vulnerable only when its settings let an attacker use the flaw.
Two routers on the same version can land in very different places. One is wide open to the internet, the other has the risky feature switched off, or sits behind an access list that blocks outsiders.
To tell them apart, check each device’s live configuration, which is how it’s set up right now. Ask three things:
A “no” to any of them can move a device a long way down your fix-first list. Done by hand, that means logging in to every device for every new CVE. Done from the live configurations, they’re done all at once.
How are they done all at once? In our case, the NetBrain Agentic NetOps Platform pulls the details of each new CVE, including the exact versions and settings that make a device vulnerable. It reads each device’s live configuration and compares the two.
A daily report and live dashboards then show which devices are vulnerable, which are already protected, and where the vulnerable ones sit. For each one, the platform shows the fix and whether it’s safe to make, and tracks progress as updates go in.
A global energy utility ran into this in 2025, when it brought management of its network and security devices in-house after 15 years with an outside provider. About 10,000 routers came with the move.
Then CISA flagged a Known Exploited Vulnerability, a flaw that attackers are already using on a type of device the utility runs everywhere. The utility board asked its group to patch any externally facing system with a flaw on that list within 24 hours.
A version check flagged all 10,000 routers as affected. The NetBrain Agentic NetOps Platform’s configuration checks looked at which management settings each router used and whether an access list limited who could reach it, and sorted the routers in about half an hour.
What the configuration checks found:
The security team sent the board the breakdown inside the 24-hour window. The utility’s security leader said the following distinction changed how he saw the feature:
You open a report that already sorts your devices by real exposure, instead of starting a sweep. Your network team works only on the devices that are vulnerable, which leaves more of your senior engineers’ time for design and architecture.
Security gets its answer too, and can tell leadership where the company stands, with evidence from the devices themselves. And because the same check can run again on a schedule, the answer is ready for the next CVE and for the next auditor.
Another CVE is always on its way. Your engineers shouldn’t have to start CVE patching with a pile of devices to chase, and security shouldn’t have to wait to tell leadership where the company stands.
Learn more about how the NetBrain Agentic NetOps Platform gives your team time back and cuts risk.
What is the difference between an affected device and a vulnerable device?
A device is affected when its software version matches the CVE. It is vulnerable only when its settings let an attacker use the flaw. Two routers on the same version can land in very different places, depending on whether the risky feature is switched on, how it is set up, and what limits who can reach it.
How do you find out which network devices a new CVE actually puts at risk?
Read the vendor advisory for the versions and settings involved, then check each device’s live configuration. Ask three things: is the feature the flaw lives in switched on, is it set up the way the flaw needs, and what limits who can reach it, such as an access list. A “no” to any of them can move a device a long way down your fix-first list.
Why is it hard to fix vulnerable routers, firewalls and VPN gateways?
These devices sit between the outside world and the rest of your network, so an attacker who gets into one can reach what is behind it. They are also hard to fix: upgrades need reboots and maintenance windows, and many teams have no full test copy of production.
Agents that show their reasoning, work within limits you set, and wait for your engineer’s approval. Plus Forrester’s math to rerun with your own numbers. Your network keeps growing, but...
The best teams at the 2026 World Cup won’t be the ones with the most stars. They’ll be the ones with the best depth and support strategy. Great teams win...
We use cookies to personalize content and understand your use of the website in order to improve user experience. By using our website you consent to all cookies in accordance with our privacy policy.