Summary
omec-project amf Vulnerable to Improper Restriction of Operations within the Bounds of a Memory Buffer
A vulnerability has been found in omec-project amf up to 2.1.1. This affects an unknown part of the component NGSetupRequest Handler. Such manipulation leads to memory corruption. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. It is best practice to apply a patch to resolve this issue.
Impact
CVE-2026-9300 has a CVSS score of 6.3 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7.1-0.20260421213846-34bc6724acc9); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-9300? CVE-2026-9300 is a low-severity security vulnerability in github.com/omec-project/amf (go), affecting versions < 1.7.1-0.20260421213846-34bc6724acc9. It is fixed in 1.7.1-0.20260421213846-34bc6724acc9.
- How severe is CVE-2026-9300? CVE-2026-9300 has a CVSS score of 6.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of github.com/omec-project/amf are affected by CVE-2026-9300? github.com/omec-project/amf (go) versions < 1.7.1-0.20260421213846-34bc6724acc9 is affected.
- Is there a fix for CVE-2026-9300? Yes. CVE-2026-9300 is fixed in 1.7.1-0.20260421213846-34bc6724acc9. Upgrade to this version or later.
- Is CVE-2026-9300 exploitable, and should I be worried? Whether CVE-2026-9300 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-9300 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-9300? Upgrade
github.com/omec-project/amfto 1.7.1-0.20260421213846-34bc6724acc9 or later.