omec-project amf up to 2.1.1 PathSwitchRequest memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in omec-project amf up to 2.1.1. Affected by this issue is some unknown functionality of the component PathSwitchRequest Handler. This manipulation causes memory corruption. This vulnerability is registered as CVE-2026-9298. Remote exploitation of the attack is possible. Furthermore, an exploit is available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in omec-project amf up to 2.1.1. It has been declared as critical. Affected by this vulnerability is some unknown processing of the component PathSwitchRequest Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-9298. The exploitation appears to be easy. The attack can be launched remotely. Technical details are unknown but a public exploit is available.
It is possible to download the exploit at github.com. It is declared as proof-of-concept.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31530). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
Website
- Product: https://github.com/omec-project/amf/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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 corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
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: PatchStatus: 🔍
0-Day Time: 🔒
Patch: github.com
Timeline
05/22/2026 Advisory disclosed05/22/2026 VulDB entry created
05/23/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 680
Status: Confirmed
CVE: CVE-2026-9298 (🔒)
GCVE (CVE): GCVE-0-2026-9298
GCVE (VulDB): GCVE-100-365245
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/22/2026 19:50Updated: 05/23/2026 16:33
Changes: 05/22/2026 19:50 (58), 05/23/2026 16:33 (1)
Complete: 🔍
Submitter: shovon0203
Cache ID: 216::103
Submit
Accepted
- Submit #811684: Linux Foundation Projects SD-Core 2.1.1 Memory Corruption (by shovon0203)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.