VulnerabilityPublished 27 May 2026Updated 28 May 2026

CVE-2026-44475: ellanetworks core · Improperly Implemented Security Check for Standard

Affects ellanetworks coreSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 1.10.0 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.10.0

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade core and ellanetworks/core to 1.10.0.

Affected software

Product	Affected	Fixed in
ellanetworkscore	Affected <1.10.0	Fixed in 1.10.0
GitHubellanetworks/core`pkg:github/ellanetworks/core`Other threats	Affected <1.10.0	Fixed in 1.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Ella Core to version 1.10.0 or later, where this vulnerability is fixed. Patch status is confirmed by the vendor stating the issue is resolved in 1.10.0. No other mitigation or temporary workaround is indicated.

Description

Ella Core versions prior to 1.10.0 contain a vulnerability where the UE Security Capabilities received in NGAP PathSwitchRequest messages are not verified against locally stored values. This allows a malicious gNB to overwrite stored UE security capabilities with arbitrary values by sending a crafted PathSwitchRequest message. The vulnerability is fixed in version 1.10.0. The CVSS score is 6.1, indicating a medium severity issue with potential integrity and availability impacts but no confidentiality loss.

Impact

An attacker controlling a malicious gNB can overwrite UE security capabilities stored by Ella Core, potentially causing integrity issues and denial of service conditions. There is no direct confidentiality impact reported. The vulnerability could disrupt normal UE security operations and affect network stability or reliability.

Summary

CVE-2026-44475 affects Ella Core, a 5G core product for private networks. Before version 1.10.0, the product fails to properly verify UE Security Capabilities in NGAP PathSwitchRequest messages against its stored values. This improper security check (CWE-358) enables a malicious gNB to overwrite the stored UE security capabilities for any UE by sending a single crafted PathSwitchRequest. This can lead to integrity and availability impacts on the affected system. The vulnerability is resolved in version 1.10.0.

References

github.com/ellanetworks/core/security/advisories/GHSA-pwfh-mqp3-pqwj (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jun 2026, 20:47 UTC

WeaknessesCWE-358

Technical details

References

Community reviews

Related threats