← Back
CVE-2026-9301
medium
CVSS 6.3
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-119) exists in github.com/omec-project/amf.
📍 Affected scope
github.com/omec-project/amf — .
🔥 Severity
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.7.1-0.20260421213846-34bc6724acc9**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/omec-project/amf to 1.7.1-0.20260421213846-34bc6724acc9ステージング環境で 1.7.1-0.20260421213846-34bc6724acc9 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/omec-project/amf
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.1-0.20260421213846-34bc6724acc9"}]}]
References
- web https://nvd.nist.gov/vuln/detail/CVE-2026-9301
- web https://github.com/omec-project/amf/issues/678
- web https://github.com/omec-project/amf/pull/666
- web https://github.com/omec-project/amf
- web https://vuldb.com/submit/811842
- web https://vuldb.com/vuln/365248
- web https://vuldb.com/vuln/365248/cti
- web https://github.com/advisories/GHSA-qm7q-rcm2-3frc
- web [email protected]
- web https://github.com/omec-project/amf/commit/34bc6724acc97dba1f8691e586da95b042cb612d