Quick answers
- Is CVE-2026-44474 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44474 being exploited in the wild.
- How severe is CVE-2026-44474?
- Low severity, with a CVSS score of 3.7, published 27 May 2026.
- Which products and versions are affected?
- Ella Networks Ella Core < 1.10.0; github.com/ellanetworks/core (Go) < 1.10.0, SEMVER:introduced=0,fixed=1.10.0.
- Is there a fix for CVE-2026-44474?
- Yes. github.com/ellanetworks/core (Go): upgrade to 1.10.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44474 attacked?
- It is attacked from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-44474?
- Check whether you run Ella Networks Ella Core or github.com/ellanetworks/core (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/ellanetworks/core (Go): upgrade to 1.10.0 or later
go get github.com/ellanetworks/core@v1.10.0
Technical details
Ella Core does not properly enforce the 3GPP TS 33.501 §6.9.5.1 standard regarding concurrent security procedures. Specifically, the system may send a NAS Security Mode Command while an N2 handover is still pending, or vice versa. This concurrency creates a KgNB key mismatch between the User Equipment (UE) and the target gNB, causing the handover to fail. Exploitation requires a specific race condition involving a stalled gNB and a re-registration event. The issue is addressed in version 1.10.0 by blocking concurrent Security Mode Command and N2 handover procedures.
Affected products
- Ella Networks core < 1.10.0
Identifiers
- CVE-2026-44474
- GHSA-mc29-hmx6-856q
- GO-2026-5502
Timeline
- 2026-05-06: disclosed: Initial disclosure to vendor
- 2026-05-11: advisory: GitHub Advisory published
- 2026-05-27: other: NVD published date