CVE-2026-32319
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. Prior to 1.5.1, Ella Core panics when processing a malformed integrity protected NGAP/NAS message with a length under 7 bytes. 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. 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 confidenceElla Core 5G core panics when parsing malformed integrity-protected NGAP/NAS messages with length under 7 bytes. The vulnerability is in the message validation logic, which lacks proper bounds checking before processing message headers. An unauthenticated attacker can send crafted messages to crash the process, causing denial of service for all connected subscribers.
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.5.1CVSS 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.
-
Verify Ella Core versionUse the system's package manager or run 'ella --version' or check /opt/ellanetworks/core/version to determine the installed Ella Core versionAffected if Installed version is less than 1.5.1
-
Confirm Ella Core service is runningCheck if the Ella Core 5G core process is active and serving connections (for example, using 'systemctl status ellacore' or process listing commands)Affected if The Ella Core service is running and processing NGAP/NAS messages (this is the default operational state of the core)
-
Inspect for crash or panic logsReview system logs, core dump directories, or Ella Core application logs for recent panics or unexpected process terminations related to message parsingAffected if Recent crash logs indicate the process panicked while parsing NGAP/NAS messages, especially messages with unusually small length values
You are affected if Ella Core version is below 1.5.1 AND the core service is running with NGAP/NAS message processing enabled, particularly if crash logs show panics during message header validation.
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.5.1
Upgrade to Ella Core version 1.5.1 or later to obtain the patch. If immediate upgrading is not feasible, implement network-level filtering to block malformed NGAP/NAS messages before they reach the core.
Ella Core 1.5.1
- Verify current Ella Core version by checking the installed package or service version
- Obtain Ella Core version 1.5.1 from the official source (github.com) or your distribution channel
- Review release notes for version 1.5.1 to understand any changes or requirements
- Create a backup of the current configuration and any persistent data
- Test the upgrade in a staging or test environment before production deployment
- Stop the Ella Core service gracefully
- Install version 1.5.1 using your deployment method (package manager, container, or binary replacement)
- Verify the service starts successfully and logs no errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32319 — 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-32319 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