Cisco Inode Manager
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Cisco Inode Manager.
By the Year
In 2026 there have been 0 vulnerabilities in Cisco Inode Manager. Last year, in 2025 Inode Manager had 1 security vulnerability published. Right now, Inode Manager is on track to have less security vulnerabilities in 2026 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 1 | 10.00 |
| 2024 | 1 | 7.50 |
It may take a day or so for new Inode Manager vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Cisco Inode Manager Security Vulnerabilities
Unauth RCE in Erlang/OTP SSH Server <27.3.3
CVE-2025-32433
10 - Critical
- April 16, 2025
Erlang/OTP is a set of libraries for the Erlang programming language. Prior to versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20, a SSH server may allow an attacker to perform unauthenticated remote code execution (RCE). By exploiting a flaw in SSH protocol message handling, a malicious actor could gain unauthorized access to affected systems and execute arbitrary commands without valid credentials. This issue is patched in versions OTP-27.3.3, OTP-26.2.5.11, and OTP-25.3.2.20. A temporary workaround involves disabling the SSH server or to prevent access via firewall rules.
Missing Authentication for Critical Function
Cisco iNode TLS Hijack via Static KeyArbitrary Traffic & DoS
CVE-2024-20323
7.5 - High
- July 17, 2024
A vulnerability in Cisco Intelligent Node (iNode) Software could allow an unauthenticated, remote attacker to hijack the TLS connection between Cisco iNode Manager and associated intelligent nodes and send arbitrary traffic to an affected device. This vulnerability is due to the presence of hard-coded cryptographic material. An attacker in a man-in-the-middle position between Cisco iNode Manager and associated deployed nodes could exploit this vulnerability by using the static cryptographic key to generate a trusted certificate and impersonate an affected device. A successful exploit could allow the attacker to read data that is meant for a legitimate device, modify the startup configuration of an associated node, and, consequently, cause a denial of service (DoS) condition for downstream devices that are connected to the affected node.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Cisco Inode Manager or by Cisco? Click the Watch button to subscribe.
