Vulnerability in github.com/omec-project/amf (CVE-2026-8781)
Summary
Vulnerability in github.com/omec-project/amf (CVE-2026-8781). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.2.0 or later.
Original description
The description as published by the source.
A security flaw has been discovered in omec-project amf up to 2.1.3-dev. The impacted element is the function RANConfiguration of the file ngap/handler.go. The manipulation results in null pointer dereference. The attack may be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 2.2.0 is sufficient to resolve this issue. Upgrading the affected component is recommended. The same pull request fixes multiple security issues.
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-8781 has been found in github.com/omec-project/amf.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/omec-project/amf to 2.2.0 or later.
If unsure, ask your IT team or search "github.com/omec-project/amf CVE-2026-8781" on the vendor's site.
CVE-2026-8781 (github.com/omec-project/amf) — CWE-404 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 2.2.0 — 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-404) exists in github.com/omec-project/amf.
Check the vendor advisory for the affected versions of github.com/omec-project/amf.
Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.2.0.
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 2.2.0ステージング環境で 2.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- patch github.com
- report github.com
- report vuldb.com
- web github.com