Verax NMS prior to 2.1.0 has multiple security bypass vulnerabilities
Priority MEDIUM 42CWE-863Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-863.
Summary
Verax NMS prior to 2.1.0 has multiple security bypass vulnerabilities
Why it matters now
EPSS 0.01514 74th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | — | all versions | — | No fix listed | CNA |
- — Vendor— Affected all versions Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:veraxsystems:network_management_system:*:*:*:*:*:*:*:* | before 2.1.0 | Vulnerable | Veraxsystems |
- cpe:2.3:a:veraxsystems:network_management_system:*:*:*:*:*:*:*:* Versions before 2.1.0 Vulnerable ·Veraxsystems
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2013-1350
- 2026-10-03 Alias added: GHSA-78qw-wh98-5mv5
References
—
More Veraxsystems Network Management System vulnerabilities
- TI-2013-01188 Verax NMS prior to 2.1.0 uses an encryption key that is hardcoded in a JAR archive. CVSS 3.1HIGH 7.5
- TI-2013-01187 Verax NMS prior to 2.10 allows authentication via the encrypted password without knowing the cleartext password. CVSS 3.1MEDIUM 5.9
- TI-2013-01434 Verax NMS prior to 2.1.0 leaks connection details when any user executes a Repair Table action CVSS 3.1MEDIUM 5.3
Sources
- CVE-2013-1350 · CVE Program
- CVE-2013-1350 · NVD
- FIRST EPSS
- GHSA-78qw-wh98-5mv5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences