How severe is GHSA-6gm8-3g4h-w82m?

GHSA-6gm8-3g4h-w82m has a CVSS score of 5.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6gm8-3g4h-w82m?

GHSA-6gm8-3g4h-w82m affects the following packages: github.com/ellanetworks/core (Go). Ecosystems affected: Go.

How do I fix GHSA-6gm8-3g4h-w82m?

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.

How do I detect GHSA-6gm8-3g4h-w82m in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ellanetworks/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6gm8-3g4h-w82m if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-6gm8-3g4h-w82m?

O3 pinpoints whether GHSA-6gm8-3g4h-w82m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6gm8-3g4h-w82m actively exploited in the wild?

No public exploit code has been indexed for GHSA-6gm8-3g4h-w82m yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-6gm8-3g4h-w82m?

GHSA-6gm8-3g4h-w82m is classified as NULL Pointer Dereference (CWE-476). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6gm8-3g4h-w82m published, and has it been updated?

GHSA-6gm8-3g4h-w82m was published on April 1, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-6gm8-3g4h-w82m

MEDIUM

GHSA-6gm8-3g4h-w82m is a medium-severity (CVSS 5.8) NULL Pointer Dereference vulnerability in github.com/ellanetworks/core. O3 Security confirms whether GHSA-6gm8-3g4h-w82m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Ella Core Panics Upon NGAP handover failure

Also known asCVE-2026-34761GO-2026-5177

Published

Apr 1, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/ellanetworks/core

Real-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

Summary

Ella Core panics when processing a NGAP handover failure message.

Impact

If an attacker can force a gNodeB to send NGAP handover failure messages to Ella Core, the process will crash, thereby disrupting service for all connected subscribers.

Fix

Improve guards in NGAP handover handlers.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/ellanetworks/core`	all versions	1.8.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ellanetworks/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
How O3 protects you
O3 pinpoints whether GHSA-6gm8-3g4h-w82m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6gm8-3g4h-w82m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary Ella Core panics when processing a NGAP handover failure message. ## Impact If an attacker can force a gNodeB to send NGAP handover failure messages to Ella Core, the process will crash, thereby disrupting service for all connected subscribers. ## Fix Improve guards in NGAP handover handlers.

O3 Security · Impact-Aware SCA

Is GHSA-6gm8-3g4h-w82m in your dependencies?

O3 detects GHSA-6gm8-3g4h-w82m across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works