dbcve.org
CWE-358Weakness · CWE-358

CVE-2026-44473

HIGH · 7.1 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
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.10.0, a radio with a valid NG Setup can send a forged PDUSessionResourceSetupResponse carrying any UE's AMF-UE-NGAP-ID. Ella Core does not verify the message arrived on the SCTP association bound to that UE's logical NG-connection, then creates a GTP tunnel towards that radio. This vulnerability is fixed in 1.10.0.

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

In Ella Core prior to 1.10.0, a radio node with a valid NG Setup can send a forged PDUSessionResourceSetupResponse containing any UE's AMF-UE-NGAP-ID. The core fails to verify that the message arrived on the SCTP association bound to that UE's logical NG-connection, allowing the attacker to trigger creation of GTP tunnels toward their radio and intercept that UE's traffic.

MitigationUpgrade to Ella Core version 1.10.0 or later, which implements verification that PDUSessionResourceSetupResponse messages arrive on the correct SCTP association bound to the UE's logical NG-connection.

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

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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/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
    Locate the installed Ella Core software and retrieve its version number (typically available via CLI command, system information, or package metadata)
    Affected if Version is prior to 1.10.0 (e.g., 1.9.x, 1.8.x, etc.)
  2. Confirm NG Setup configuration
    Check whether NG Setup is configured and active on the radio node (verify the presence of NG interface configuration and active SCTP associations)
    Affected if NG Setup is configured and operational, creating SCTP associations for UE connections
  3. Verify SCTP association binding
    Inspect logs or configuration to determine if PDUSessionResourceSetupResponse messages are validated against the SCTP association bound to the UE's logical NG-connection
    Affected if No verification is performed; the system accepts PDUSessionResourceSetupResponse on any SCTP association for the given AMF-UE-NGAP-ID
  4. Review GTP tunnel creation logs
    Check system logs for PDUSessionResourceSetupResponse processing and GTP tunnel establishment events
    Affected if GTP tunnels are being created without validation that the response originated from the correct SCTP association

The environment is affected if Ella Core version is prior to 1.10.0 AND NG Setup is configured, because the vulnerability allows forged PDUSessionResourceSetupResponse messages to trigger unauthorized GTP tunnel creation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Ella Core version 1.10.0 or later, which implements verification that PDUSessionResourceSetupResponse messages arrive on the correct SCTP association bound to the UE's logical NG-connection.

Recommended fix Moderate confidence

1.10.0

  1. 1. Identify the current version of Ella Core deployed in the private 5G network
  2. 2. Download Ella Core version 1.10.0 or later from the official repository (github.com)
  3. 3. Review release notes for version 1.10.0 to understand any migration requirements
  4. 4. Back up the current Ella Core configuration and state
  5. 5. Stop the Ella Core services
  6. 6. Install Ella Core version 1.10.0
  7. 7. Restore or reconfigure the backed-up settings
  8. 8. Start Ella Core services and verify the NG Setup procedure works correctly
Caveat No breaking change information provided in the advisory; upgrade should be straightforward

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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