dbcve.org
Ella CoreApplication · Ellanetworks

CVE-2026-32320

HIGH · 7.5 CVSS v3.1 Published 2026-03-13
Fix available
A fix is available. Upgrade to 1.5.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Ella Core is a 5G core designed for private networks. Prior to 1.5.1, Ella Core panics when processing a PathSwitchRequest containing UE Security Capabilities with zero-length NR encryption or integrity protection algorithm bitstrings, resulting in a denial of service. An attacker able to send crafted NGAP messages to Ella Core can crash the process, causing service disruption for all connected subscribers. No authentication is required. This vulnerability is fixed in 1.5.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Ella Core 5G core panics when processing PathSwitchRequest messages containing UE Security Capabilities with zero-length NR encryption or integrity protection algorithm bitstrings. An attacker can send crafted NGAP messages without authentication to trigger the panic, causing process crash and denial of service for all connected subscribers.

MitigationUpgrade Ella Core to version 1.5.1 or later. Until upgrade, consider network-level filtering of malformed NGAP messages at the RAN or transport layer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ella CoreApplication
Affected:< 1.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ella Core version
    Check the installed Ella Core version using the system's package manager, software inventory command, or Ella Core's CLI version command (e.g., 'ella --version' or 'show version'). Compare the version number against the affected range (< 1.5.1).
    Affected if The installed version is below 1.5.1
  2. Confirm NGAP interface is enabled
    Inspect Ella Core configuration for NGAP (Next Generation Application Protocol) settings. Look for NGAP peer configurations, specifically related to gNB/RAN connectivity. Check if PathSwitchRequest message processing is permitted in the NGAP configuration.
    Affected if NGAP interface is enabled and configured to accept PathSwitchRequest messages from RAN nodes
  3. Check for crash or panic logs
    Review Ella Core system logs, kernel logs, or application crash logs for recent panic events related to 'PathSwitchRequest', 'UE Security Capabilities', or NGAP processing. Look for timestamps and error patterns matching the described vulnerability.
    Affected if Recent crash logs show panic related to PathSwitchRequest or UE Security Capabilities processing
  4. Verify RAN/transport layer exposure
    Determine if the NGAP interface is exposed to untrusted or unauthenticated gNB/RAN nodes. Check access control lists, firewall rules, or RAN peer authentication settings. The vulnerability can be triggered by messages sent without authentication.
    Affected if NGAP interface accepts connections from untrusted or unauthenticated sources
  5. Review subscriber impact
    Check system logs or subscriber management records for any recent service disruptions, mass disconnect events, or process restarts that correlate with NGAP PathSwitchRequest traffic.
    Affected if Recent subscriber outages coincide with PathSwitchRequest message traffic

You are affected if Ella Core version is below 1.5.1 AND the NGAP interface is enabled to process PathSwitchRequest messages from accessible RAN nodes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.5.1 or later
Fixed in 1.5.1
Interim mitigation

Upgrade Ella Core to version 1.5.1 or later. Until upgrade, consider network-level filtering of malformed NGAP messages at the RAN or transport layer.

Recommended fix High confidence

1.5.1

  1. 1. Identify the current Ella Core version deployed in your environment
  2. 2. Retrieve Ella Core version 1.5.1 from the official distribution source (github.com or vendor repository)
  3. 3. Review release notes for version 1.5.1 to confirm the security fix for CVE-2026-32320
  4. 4. Perform a backup of the current Ella Core configuration and data
  5. 5. Stop the currently running Ella Core service
  6. 6. Install or deploy Ella Core version 1.5.1
  7. 7. Restore the configuration backup if needed
  8. 8. Start the Ella Core service

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ella Core Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data