CVE-2026-33283
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 · uneditedElla Core is a 5G core designed for private networks. Versions prior to 1.6.0 panic when processing malformed UL NAS Transport NAS messages without a Request Type. An attacker able to send crafted NAS messages to Ella Core can crash the process, causing service disruption for all connected subscribers. No authentication is required. Version 1.6.0 adds a guard when receiving an UL NAS Message without a Request Type given no SM Context.
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 confidenceElla Core 5G core software versions prior to 1.6.0 experience a panic (crash) when processing malformed UL NAS Transport NAS messages that lack a Request Type field. The vulnerability is triggered when no SM Context exists, causing the process to terminate and disrupt service for all connected subscribers. This is a denial-of-service vulnerability exploitable by unauthenticated attackers sending specially crafted NAS messages.
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< 1.6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Ella Core installationLocate the Ellanetworks Ella Core software on your system. Check for installed packages or running processes related to 'ella', 'ella-core', or 'Ellanetworks'. On Linux systems, you may use commands like 'dpkg -l | grep ella' or 'rpm -qa | grep ella'. Check running processes with 'ps aux | grep -i ella'.Affected if Ellanetworks Ella Core software is present on the system
-
Determine installed versionRun the version command for Ella Core. Common methods include 'ella-core --version', 'ella --version', or checking the package metadata with 'dpkg -l ella-core' or 'rpm -qi ella-core'. Compare the version number against the affected range of versions prior to 1.6.0.Affected if The installed version is lower than 1.6.0 (for example, 1.5.x, 1.4.x, etc.)
-
Verify UL NAS Transport processing is activeCheck if the 5G core functions are running and processing NAS messages. Review configuration files in /etc/ella/ or /opt/ella/ for NAS transport settings. Use 'netstat' or 'ss' to verify the service is listening on expected 5G interfaces (typically SCTP or UDP ports for N1/N2 interfaces).Affected if The Ella Core service is running and UL NAS Transport message processing is enabled
-
Check for crash or panic logsSearch system logs for crash or panic events related to NAS message processing. Common log locations include /var/log/ella/, /var/log/syslog, or journalctl output. Look for entries containing 'UL NAS', 'NAS Transport', 'panic', 'crash', 'SM Context', or 'Request Type'. Use commands like 'grep -i 'panic\|crash' /var/log/ella/*.log' or 'journalctl -u ella-core | grep -i nas'.Affected if Recent crash or panic logs mention UL NAS Transport processing failures or missing Request Type fields
You are affected if Ellanetworks Ella Core is installed with a version prior to 1.6.0 and the UL NAS Transport message processing feature is active, as malformed messages lacking a Request Type will trigger a process crash.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.6.0
Upgrade Ella Core to version 1.6.0 or later, which implements proper validation guards to handle UL NAS messages without a Request Type. If immediate upgrade is not possible, consider network-level filtering to block malformed NAS messages at the perimeter.
Ella Core 1.6.0
- 1. Identify all deployed instances of Ella Core in the environment.
- 2. Check the current version of each Ella Core deployment using system information or version commands.
- 3. For any instance running a version prior to 1.6.0, plan and schedule an upgrade to version 1.6.0 or later.
- 4. Before upgrading, review release notes for version 1.6.0 to understand any changes in configuration or behavior.
- 5. Perform the upgrade following the vendor's standard upgrade procedure for Ella Core.
- 6. After upgrade, verify that the service is running correctly and test UL NAS Transport message processing.
- 7. Monitor the system to ensure the NULL pointer dereference no longer occurs with malformed messages.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33283 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33283 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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