CVE-2021-1132 is a medium severity (CVSS 5.3) directory traversal flaw in the web management interface and HTTP APIs of Cisco Network Services Orchestrator. An unauthenticated remote attacker could read sensitive files. NSO 5.3 should move to 5.3.3 and 5.4 to 5.4.1. NSO 5.2 and earlier are not vulnerable.
What's affected
- Cisco NSO 5.3 and 5.4, per the advisory.
- Fixed: 5.3.3 and 5.4.1. NSO 5.2 and earlier are not vulnerable.
- Cisco states there are no workarounds.
The record scores it 5.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Check the NSO version with the ncs --version command on the host, and compare with the fixed releases.
What to do now
- Find NSO hosts.
- Run
ncs --version. - Upgrade 5.3 to 5.3.3 and 5.4 to 5.4.1, or later.
- Restrict access to the web interface and APIs to management networks.
- Review files readable by the NSO service account.
After you patch, record the new version for Cisco NSO in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The record maps the flaw to CWE-35, path traversal. The interface does not validate user supplied input well enough, so special directory sequences in a request reach files outside the intended folder.
No login is needed, which is why it is worth fixing despite the medium score. NSO holds network configuration, so exposed files may include sensitive data.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Does the attacker need credentials?
No. The record describes an unauthenticated, remote attacker.
How do I find every place Cisco NSO is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
Last reviewed: 19 October 2026.