Quick answers
- Is CVE-2026-107242 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107242 being exploited in the wild.
- How severe is CVE-2026-107242?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Versa Networks VOS.
- Is there a fix for CVE-2026-107242?
- No fixed version is recorded yet. Disable the Node.js web service after initial provisioning of the VOS device is complete, as recommended in Versa's security hardening guide for Hubs, Branches, and Controllers. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-107242 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-107242?
- Check whether you run Versa-Networks VOS. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Disable the Node.js web service after initial provisioning of the VOS device is complete, as recommended in Versa's security hardening guide for Hubs, Branches, and Controllers.
Technical details
The Node.js web service on VOS uses UUIDv1 for session identifier generation, which is derived from system date, time, and MAC address. This makes successive identifiers predictable and differ only marginally. An attacker capable of predicting session IDs could perform session hijacking; however, the vulnerability is not exploitable if the Node.js web service is disabled after initial provisioning.
Affected products
- Versa Networks VOS
Timeline
- 2026-11-10: disclosed