Quick answers
- Is CVE-2026-93308 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93308 being exploited in the wild.
- How severe is CVE-2026-93308?
- Medium severity, with a CVSS score of 4.3, published 18 September 2026.
- Which products and versions are affected?
- O-RAN-SC SMO OAM 2025-06-10.
- Is there a fix for CVE-2026-93308?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. 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-93308 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-93308?
- Check whether you run O-RAN-SC SMO OAM at an affected version. 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.
Technical details
The vulnerability is a CWE-770 (allocation of resources without limits) in the VES Collector component of O-RAN-SC SMO OAM 2025-06-10. An attacker can conduct a low-and-slow distributed denial-of-service attack by sending a high volume of heartbeat events with varying source identifiers and sequence numbers to the VES event listener endpoint (port 8080/eventListener/v7). The attack is network-accessible and requires no authentication. By maintaining many concurrent connections and sending events at controlled intervals, an attacker can exhaust the collector's memory and processing capacity, preventing it from handling legitimate monitoring events. Patches or vendor mitigations were not available at the time of advisory publication.
Affected products
- O-RAN-SC SMO OAM 2025-06-10
Timeline
- 2026-09-18: disclosed
- other: Exploit proof-of-concept made public; vendor informed via bug report with no response