TCP/IP Stack Vulnerabilities: Forescout Confirms 99 Flaws in 10 Stacks, Few Fixes So Far, and How to Contain Devices You Can't Patch
Forescout confirmed 99 vulnerabilities across 10 TCP/IP stacks, and only five of 34 proprietary-stack reports are fixed. Here is what is confirmed, what is not, and how to contain devices you cannot patch.
Where Worldwide
On this page 9 sections
Forescout researchers say they confirmed 99 vulnerabilities across 10 TCP/IP stacks. A TCP/IP stack is the networking code that lets connected devices, such as building controllers, send and receive traffic. This matters to businesses because few fixes exist: Forescout says that of 34 reports affecting proprietary stacks, only five have been fixed to date. That means devices already on your network may stay vulnerable, with no patch to install.
What Forescout found in TCP/IP stacks
Forescout published the findings in a research write-up, and Help Net Security reported on it on November 16, 2026. These are the confirmed numbers from the two sources:
- 99 vulnerabilities in total: 33 rediscovered and 66 new.
- 10 TCP/IP stacks affected.
- 52% are critical or high severity, according to Forescout.
- 34 reports affect proprietary stacks, and only five of those have been fixed to date.
Forescout links the work directly to AI. Daniel dos Santos, VP of Research at Forescout, said: "Our research demonstrates that AI is changing the economics of vulnerability discovery". Our reading: if finding bugs in this kind of code gets cheaper and faster for researchers, it gets cheaper and faster for attackers too. The sources we reviewed do not say which AI tools were used or how.
CVE-2026-120596: the Ethernut (Nut/OS) flaw
One of the published examples is CVE-2026-120596 in Ethernut v5.1, which uses the Nut/OS TCP/IP stack. Forescout describes it like this: "A remotely exploitable denial-of-service vulnerability exists in the TCP options parser of Nut/OS."
In plain terms, someone who can send network traffic to an affected device could make it stop working, without being in the room with it.
What we could not confirm: a severity score for this CVE, a fixed Ethernut version, or which commercial products ship Ethernut v5.1. If you find it in your environment, treat it as unpatched until the maker of your device tells you otherwise.
Hardcoded admin credentials that cannot be changed
Forescout's report also lists "hardcoded administrator credentials that cannot be changed for web and shell management". The material we reviewed does not let us confirm which product this applies to, so we will not guess.
The lesson applies widely anyway. When a login is built into the firmware, changing passwords does nothing. That leaves two controls: limiting who can reach the web and shell management interfaces, and replacing the device.
Building automation controllers: APOGEE, Desigo and TALON
Forescout's report notes that "several building automation controllers in the APOGEE, Desigo and TALON product lines run Nucleus NET". Building automation controllers are often put in by a facilities or controls contractor rather than IT, which is one reason they get left out of patch plans.
From what we reviewed, we do not know which Nucleus NET findings affect these controllers, which models or firmware versions are involved, or whether fixes exist. If your building uses these product lines, ask your controls contractor or the vendor directly.
What is confirmed and what is not
| Question | Status |
|---|---|
| 99 vulnerabilities across 10 TCP/IP stacks | Confirmed by Forescout |
| 33 rediscovered, 66 new | Confirmed by Forescout |
| 52% critical or high severity | Confirmed by Forescout |
| Only five of 34 proprietary-stack reports fixed | Confirmed by Forescout, as of its report |
| CVE-2026-120596 is a remote denial-of-service flaw in Nut/OS | Confirmed by Forescout |
| Fixed version for Ethernut v5.1 | Not known |
| Attacks using these flaws in the wild | Not reported in the sources we reviewed |
| Full list of the 10 stacks and affected products | Not in the material we reviewed |
Why this matters for a company network
Most businesses patch laptops, servers and firewalls on a schedule. Devices built on these stacks are different. Building controllers and other network-connected equipment often run for years on firmware nobody touches. If the stack has a flaw and the maker has not shipped a fix, there is nothing to install.
Barry Mainz, Forescout's CEO, was direct about the priority: "Containing risk, rather than patching, must be the priority". For a business, containing risk means two things. People who should not reach an unpatched device cannot reach it. And if the device is crashed or taken over, the damage stays in one corner of the network.
This is the problem we covered in Who Is Patching the Software That Runs Your Business?: a fix only helps if someone owns the device and applies it. When no fix exists, as with CVE-2026-120596 in Ethernut v5.1, the plan is isolation and then replacement.
What to do this week
The sources give no fixed versions to install, so this checklist is about finding devices and containing them.
| Step | What to do | How to check |
|---|---|---|
| 1. Inventory | List every network-connected device that is not a PC, phone or server, including building controllers | Match every address in your switch tables or DHCP leases to a device and an owner |
| 2. Look for named products | Search for Ethernut v5.1 and for controllers in the APOGEE, Desigo and TALON lines | Check asset lists, contractor paperwork and device labels |
| 3. Ask the vendor | Ask whether the device is affected by Forescout's TCP/IP stack findings and whether a fix exists | Get a written answer that gives either a firmware version or a clear statement that there is no fix |
| 4. Remove internet exposure | Make sure no management page or device port can be reached from the internet | Scan your public IP addresses from outside, or ask your provider to do it |
| 5. Segment | Move these devices to their own VLAN, with firewall rules that allow only the traffic they need | Confirm an ordinary office laptop cannot reach the device |
| 6. Lock down management | Allow web and shell management only from one admin system or jump host | Try connecting from a non-admin machine; the connection should fail |
| 7. Watch for crashes | A denial-of-service flaw shows up as unexplained reboots or dropouts | Turn on logging or uptime monitoring for these devices |
| 8. Plan replacement | Set aside budget to retire devices that will never get a fix | Record each device's vendor support status and end date |
If you want help with segmentation and firewall rules, that is the core of our security hardening work. We also design self-hosted infrastructure with isolation built in from the start.
TCP/IP stack vulnerability questions people are asking
What is a TCP/IP stack?
It is the part of a device's software that handles network communication. Anyone who can send traffic to the device can reach a flaw in it.
What did Forescout find?
99 vulnerabilities across 10 TCP/IP stacks: 33 rediscovered and 66 new, with 52% rated critical or high severity.
Is there a patch?
In most cases, not yet. Of 34 reports affecting proprietary stacks, only five have been fixed to date. The sources do not give a fixed version for Ethernut v5.1.
What is CVE-2026-120596?
A denial-of-service flaw that can be exploited remotely. It is in the TCP options parser of Nut/OS, the stack Ethernut v5.1 uses.
Are building automation controllers affected?
Forescout notes that several controllers in the APOGEE, Desigo and TALON lines run Nucleus NET. What we reviewed does not say which models or flaws apply, so ask your vendor.
Are these flaws being exploited?
The sources we reviewed do not report attacks in the wild. That does not mean no attacks have happened.
How do I protect devices I cannot patch?
Keep them off the internet, put them on their own network segment, limit management access to one admin system, and plan to replace them.
Did AI find these bugs?
Forescout presents the research as evidence that AI is changing the economics of vulnerability discovery. The sources we reviewed do not say which AI tools were used.
The bigger lesson
Patching is only one control, and for many devices it is not available at all. Know what is on your network, who owns it and what it can reach. The pace of bug discovery is speeding up, and the devices nobody looks after will be found first.
Need help isolating devices you can't patch? See our security hardening services or request a quote.
Get security alerts like this by email, plus our free checklist, at /security-alerts.
Sources: Forescout Research Labs: Finding critical infrastructure bugs; Help Net Security.
Have a question about this article?
Ask it here and we will answer you directly by email. Questions are private, never posted.
Security alerts by email
Hear about the next one first.
When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.
Want a result like this?
Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.
Get a Tech QuoteKeep reading
Check Point Zero-Day Fix
CISA added Check Point CVE-2026-123039 to its exploited list on November 13, 2026. Here is the temporary fix f...
Check Point Vulnerability CVE-2026-123039: Exploited Gateway Flaw Gives Attackers Root, Wiper and Backdoors Found, and the Jumbo Hotfix Takes to Install
Check Point confirmed attackers used a root flaw in Gaia's DynamicCLI service against a couple of dozen custom...
Windows Remote Desktop Vulnerability: Microsoft Fixes Four RDP Client Flaws a Malicious Server Could Trigger, and the November 2026 Builds to Install
On November 10, 2026, Microsoft fixed four flaws in the Windows Remote Desktop client. Three can be triggered...