Categories
CVE-2026-34761 medium CVSS 5.8

Vulnerability in github.com/ellanetworks/core (CVE-2026-34761)

Summary

Vulnerability in github.com/ellanetworks/core (CVE-2026-34761). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.8.0 or later.

Original description

The description as published by the source.

Ella Core is a 5G core designed for private networks. Prior to version 1.8.0, Ella Core panics when processing a NGAP handover failure message. An attacker able to cause a gNodeB to send NGAP handover failure messages to Ella Core can crash the process, causing service disruption for all connected subscribers. This issue has been patched in version 1.8.0.

Source: NIST National Vulnerability Database 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-34761 has been found in github.com/ellanetworks/core.
Risk of unauthorized operations or information disclosure. CVSS score: 5.8/10.
What to do: upgrade github.com/ellanetworks/core to 1.8.0 or later.
If unsure, ask your IT team or search "github.com/ellanetworks/core CVE-2026-34761" on the vendor's site.

CVE-2026-34761 (github.com/ellanetworks/core) — CWE-476 / CVSS v3 5.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.8.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.

❓ What is the problem

A vulnerability (CWE-476) exists in github.com/ellanetworks/core.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/ellanetworks/core.

🔥 Severity

Severity: Medium (CVSS 5.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.8.0.

🛡️ 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/ellanetworks/core' . 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

  1. 1
    Identify exposure identify
    grep -r 'github.com/ellanetworks/core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/ellanetworks/core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/ellanetworks/core to 1.8.0

    ステージング環境で 1.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/ellanetworks/core
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.8.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details