CVE-2026-15720
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 · uneditedIn Open5GS through version 2.7.7 a pre-authentication heap out-of-bounds read in the AMF NAS 5GS mobile-identity handler may result in subscriber-wide denial of service.
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 · moderate confidenceOpen5GS through version 2.7.7 contains a pre-authentication heap out-of-bounds read vulnerability in the AMF component's NAS 5GS mobile-identity handler. The flaw allows an unauthenticated attacker to trigger the vulnerability by sending specially crafted NAS messages containing malformed mobile identities, leading to a denial of service affecting all subscribers.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Open5GS installation and versionRun 'open5gs --version' or check the package manager for the installed Open5GS version (e.g., 'dpkg -l | grep open5gs' or 'rpm -qa | grep open5gs')Affected if The installed version is 2.7.7 or any earlier version of Open5GS
-
Verify AMF component is enabledCheck the Open5GS configuration file (typically /etc/open5gs/amf.yaml) or run 'open5gs-amfd --version' to confirm the AMF component is installed and configuredAffected if The AMF component is present and configured in the Open5GS deployment
-
Confirm AMF network exposureInspect the AMF configuration file for the 'sbi:' or 'ngap:' bind address. Check if the AMF is bound to a public or untrusted IP address rather than localhost or an internal network interfaceAffected if The AMF service is listening on an IP address reachable from untrusted networks (0.0.0.0 or public IP rather than 127.0.0.1 or internal-only interface)
-
Review AMF logs for crash indicatorsCheck system logs (journalctl -u open5gs-amfd or /var/log/open5gs/amf.log) for sudden process exits, segmentation faults, or error messages related to NAS mobile-identity processingAffected if The AMF process has crashed or is exhibiting instability that correlates with external NAS message reception
A user is affected if they are running any version of Open5GS up to and including 2.7.7 with the AMF component exposed to untrusted network sources, since the vulnerability is triggerable via malformed NAS messages before any authentication.
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.
From vendor dataUpgrade to a patched version of Open5GS once available. If immediate patching is not possible, consider network-level access controls to limit exposure of the AMF interface to untrusted sources.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15720 — 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-15720 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