Ella Core Panics Upon NGAP handover failureGHSA-6gm8-3g4h-w82m
MEDIUMGHSA-6gm8-3g4h-w82m is a medium-severity (CVSS 5.8) NULL Pointer Dereference vulnerability in github.com/ellanetworks/core. A fix is available for github.com/ellanetworks/core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6gm8-3g4h-w82m.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/ellanetworks/coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ellanetworks/core | all versions | 1.8.0go get github.com/ellanetworks/core@v1.8.0 |
Affected Products
ella coreellanetworksDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ellanetworks/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/ellanetworks/core to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6gm8-3g4h-w82m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-6gm8-3g4h-w82m in your dependencies?
Find it across Go, including transitive dependencies.