Buffer Overflow in github.com/omec-project/amf (CVE-2026-9301)
Summary
Vulnerability in github.com/omec-project/amf (CVE-2026-9301). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.7.1-0.20260421213846-34bc6724acc9 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) 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-9301 has been found in github.com/omec-project/amf.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade github.com/omec-project/amf to 1.7.1-0.20260421213846-34bc6724acc9 or later.
If unsure, ask your IT team or search "github.com/omec-project/amf CVE-2026-9301" on the vendor's site.
CVE-2026-9301 (github.com/omec-project/amf) — CWE-119 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.7.1-0.20260421213846-34bc6724acc9 — apply immediately
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-119) exists in github.com/omec-project/amf.
Check the vendor advisory for the affected versions of github.com/omec-project/amf.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 1.7.1-0.20260421213846-34bc6724acc9.
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. Run grep -r 'github.com/omec-project/amf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/omec-project/amf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/omec-project/amfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/omec-project/amf to 1.7.1-0.20260421213846-34bc6724acc9ステージング環境で 1.7.1-0.20260421213846-34bc6724acc9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory vuldb.com
- advisory vuldb.com
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- report github.com
- report vuldb.com
- web github.com
- web github.com