Is CVE-2026-93307 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-93307 being exploited in the wild.

How severe is CVE-2026-93307?

Medium severity, with a CVSS score of 4.3, published 17 September 2026.

Is there a fix for CVE-2026-93307?

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-93307 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-93307?

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.

CVE-2026-93307: O-RAN-SC SMO OAM VES Collector resource exhaustion

CVE-2026-93307 · Severity: medium · CVSS 4.3 · Published 2026-09-17

O-RAN-SC SMO OAM's VES Collector is a network management component that processes heartbeat and event messages from radio access equipment. An attacker can send specially crafted messages with excessively large padding fields to trigger uncontrolled memory allocation, causing the service to become unresponsive or crash, disrupting radio network monitoring and management.

Technologies: O-RAN-SC SMO OAM. Vendors: O-RAN-SC.

Quick answers

Is CVE-2026-93307 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-93307 being exploited in the wild.
How severe is CVE-2026-93307?: Medium severity, with a CVSS score of 4.3, published 17 September 2026.
Which products and versions are affected?: O-RAN-SC SMO OAM 2025-06-10.
Is there a fix for CVE-2026-93307?: 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-93307 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-93307?: 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 denial-of-service issue (CWE-789: Uncontrolled Allocation of Resources with External Input) in the VES Collector component of O-RAN-SC SMO OAM. The root cause is insufficient validation of the `additionalFields.padding` parameter in heartbeat event messages, allowing an attacker to inject arbitrarily large string values. A remote attacker can send HTTP POST requests to the VES event listener endpoint with increasingly large payloads to exhaust heap memory, causing the application to hang or crash. The attack requires network access to port 8080 but no authentication. Proof-of-concept code demonstrating the attack has been publicly disclosed. Patch status is unknown as the project has not yet responded to the bug report.

Affected products

O-RAN-SC SMO OAM 2025-06-10

Timeline

2026-09-17: disclosed: Vulnerability disclosed publicly; proof-of-concept code published on GitHub
2026-06-10: other: Vulnerability discovered and reported to O-RAN-SC; project has not responded

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.