# CVE-2026-93307: O-RAN-SC SMO OAM VES Collector memory allocation

> Remote attackers can cause denial of service in O-RAN SMO OAM VES Collector via uncontrolled memory allocation in additionalFields.padding.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-g643-hjfx-77g7

## What is CVE-2026-93307?

CVE-2026-93307 is a medium-severity denial of service vulnerability in O-RAN-SC SMO OAM, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in O-RAN-SC SMO OAM 2025-06-10. Affected is an unknown function of the component VES Collector. Such manipulation of the argument additionalFields.padding leads to uncontrolled memory allocation. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through a bug report but has not responded yet.

Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-93307?


## How do I fix CVE-2026-93307?

No fix has been published for CVE-2026-93307 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93307 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93307 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93307 and fix it if it is affected.

What it is: CVE-2026-93307 is a medium-severity denial of service vulnerability in O-RAN-SC SMO OAM, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93307 exists.

Affected product: O-RAN-SC SMO OAM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93307/ (Markdown: https://insights.sbomify.com/CVE-2026-93307/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93307
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93307
- OSV: https://osv.dev/vulnerability/CVE-2026-93307

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93307/
Summaries are generated and may contain mistakes; the official description above is the record.