O-RAN-SC SMO OAM 2025-06-10 VES Collector additionalFields.padding memory allocation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 1.61 |
Summary
A vulnerability was found in O-RAN-SC SMO OAM 2025-06-10. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component VES Collector. Performing a manipulation of the argument additionalFields.padding results in memory allocation. This vulnerability was named CVE-2026-93307. The attack may be initiated remotely. In addition, an exploit is available. The project was informed of the problem early through a bug report but has not responded yet.
Details
A vulnerability classified as problematic has been found in O-RAN-SC SMO OAM 2025-06-10. This affects an unknown code block of the component VES Collector. The manipulation of the argument additionalFields.padding with an unknown input leads to a memory allocation vulnerability. CWE is classifying the issue as CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. This is going to have an impact on availability.
The advisory is shared at lf-o-ran-sc.atlassian.net. This vulnerability is uniquely identified as CVE-2026-93307. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known.
The exploit is shared for download at gist.github.com. It is declared as proof-of-concept. The project was informed of the problem early through a bug report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory allocationCWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/17/2026 Advisory disclosed09/17/2026 VulDB entry created
09/17/2026 VulDB entry last update
Sources
Advisory: SMO-201Status: Not defined
CVE: CVE-2026-93307 (🔒)
GCVE (CVE): GCVE-0-2026-93307
GCVE (VulDB): GCVE-100-406593
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/17/2026 19:11Changes: 09/17/2026 19:11 (56)
Complete: 🔍
Submitter: fklement
Cache ID: 216::103
Submit
Accepted
- Submit #942297: O-RAN-SC SMO/OAM L-Release CWE-789 Memory Allocation with Excessive Size Value (by fklement)
Duplicate
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.