dbcve.org
Ella CoreApplication · Ellanetworks

CVE-2026-33282

HIGH · 7.5 CVSS v3.1 Published 2026-03-24
Fix available
A fix is available. Upgrade to 1.6.0 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. Versions prior to 1.6.0 panic when processing a malformed NGAP LocationReport message with `ue-presence-in-area-of-interest` event type and omitting the optional `UEPresenceInAreaOfInterestList` IE. 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. Version 1.6.0 added IE presence verification to NGAP message handling.

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 versions before 1.6.0 panic when processing malformed NGAP LocationReport messages containing the `ue-presence-in-area-of-interest` event type but omitting the optional `UEPresenceInAreaOfInterestList` IE. An unauthenticated attacker with network access to the NGAP interface can send crafted messages to crash the process, causing complete service disruption for all connected subscribers.

MitigationUpgrade to Ella Core version 1.6.0 or later, which adds IE presence verification to NGAP message handling to prevent the panic condition.

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.6.0

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. Check installed Ella Core version
    Run 'ella --version' or check the package version using your system package manager (dpkg, rpm, etc.)
    Affected if version is below 1.6.0
  2. Verify NGAP interface exposure
    Review network configuration to determine if the NGAP service port is listening on accessible network interfaces; check firewall rules and bind addresses
    Affected if NGAP interface is reachable from untrusted networks and Ella Core version is below 1.6.0
  3. Confirm Ella Core service is running
    Check process status using 'ps aux | grep ella' or systemd service status
    Affected if service is active and version is below 1.6.0
  4. Check NGAP LocationReport processing
    Inspect Ella Core configuration files for NGAP message handling settings related to LocationReport and ue-presence-in-area-of-interest event processing
    Affected if LocationReport processing is enabled and version is below 1.6.0

Environment is affected if Ella Core version is below 1.6.0, the service is running, and the NGAP interface is accessible to an attacker.

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.6.0 or later
Fixed in 1.6.0
Interim mitigation

Upgrade to Ella Core version 1.6.0 or later, which adds IE presence verification to NGAP message handling to prevent the panic condition.

Recommended fix High confidence

1.6.0

  1. Identify the current Ella Core version running in your environment
  2. Download Ella Core version 1.6.0 or later from the official repository
  3. Plan maintenance window as upgrade will require service restart
  4. Stop the Ella Core service gracefully
  5. Back up configuration files and database if applicable
  6. Install version 1.6.0 or latest stable release
  7. Verify the installation completed successfully
  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
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33282 — 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-33282 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