Vulnerability in O-RAN-SC SMO OAM (CVE-2026-93309)
Summary
Vulnerability in O-RAN-SC SMO OAM (CVE-2026-93309). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A vulnerability was determined in O-RAN-SC SMO OAM 2025-06-10. Affected by this issue is some unknown functionality of the component VES Collector. Executing a manipulation can lead to allocation of resources. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through a bug report but has not responded yet.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-93309 has been found in O-RAN-SC SMO OAM.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "O-RAN-SC SMO OAM CVE-2026-93309" on the vendor's site.
CVE-2026-93309 (O-RAN-SC SMO OAM) — CWE-400 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in O-RAN-SC SMO OAM.
Check the vendor advisory for the affected versions of O-RAN-SC SMO OAM.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで O-RAN-SC SMO OAM を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web gist.github.com
- web lf-o-ran-sc.atlassian.net
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web vuldb.com
- web nvd.nist.gov
- web github.com