omec-project amf Vulnerable to Improper Restriction of Operations within the Bounds of a Memory BufferGHSA-qm7q-rcm2-3frc
MEDIUMFix: omec-project/amf#666GHSA-qm7q-rcm2-3frc is a medium-severity (CVSS 6.3) Buffer Overflow vulnerability in github.com/omec-project/amf. A fix is available for github.com/omec-project/amf — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-qm7q-rcm2-3frc.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-qm7q-rcm2-3frc by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 384,189 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
github.com/omec-project/amfReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was found in omec-project amf up to 2.1.1. This vulnerability affects unknown code of the component NGReset Message Handler. Performing a manipulation results in memory corruption. The attack is possible to be carried out remotely. The exploit has been made public and could be used. It is recommended to apply a patch to fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/omec-project/amf | all versions | 1.7.1-0.20260421213846-34bc6724acc9go get github.com/omec-project/amf@v1.7.1-0.20260421213846-34bc6724acc9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/omec-project/amf, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/omec-project/amf to 1.7.1-0.20260421213846-34bc6724acc9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qm7q-rcm2-3frc is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is GHSA-qm7q-rcm2-3frc in your dependencies?
Find it across Go, including transitive dependencies.