Skip to main content

UERANSIM gNB EUVDEUVD-2026-88204

| CVE-2026-101035 MEDIUM
Uncaught Exception (CWE-248)
2026-09-28 VulDB GHSA-mc56-m68v-2mjr
5.5
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Connect to gNB as a UE
  2. Delivery
    Send crafted plain Initial NAS Registration Request
  3. Exploit
    DecodeNasMessage throws on unmodeled type/IEI
  4. Execution
    Uncaught exception on bare NtsTask thread
  5. Impact
    gNB process terminates (DoS)

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A10:2025 - Mishandling of Exceptional Conditions
ASVS 5.0
V16 - Security Logging and Error Handling Exception handling completeness
Exploitation Conditions

Requires network/radio reachability to a running UERANSIM gNB (nr-gnb) at version <=3.3.0 that accepts UE connections. The attacker sends a plain (NOT_PROTECTED) Initial NAS message - the vulnerable path only decodes unprotected Registration Requests during AMF slice selection, so security-protected messages are passed through untouched and do not reach the throwing decoder. No authentication is required (PR:N) because Initial Registration precedes NAS security establishment, and no user interaction is needed. Limiting factors: exploitation only affects deployments of the UERANSIM simulator (predominantly test/lab/research environments rather than production networks), and impact is confined to crashing the gNB process (availability), with no confidentiality or integrity effect.

Impact

This is a low-to-moderate real-world risk: a denial-of-service, not a code-execution or data-exposure flaw. The vendor CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, VC:N/VI:N/VA:L/E:P, 6.9) and CWE-248 (uncaught exception) agree with the source-code evidence: DecodeNasMessage throws on a NAS message type or IEI it does not model, nothing in the NGAP task catches it, and because NtsTask runs onLoop on a bare thread the exception terminates the entire gNB process. So impact is availability-only - I actually lean toward A:H (the whole gNB dies) rather than the vendor's VA:L, which understates a full-process crash. There is NO confidentiality impact, which directly contradicts the 'Information Disclosure' tag (VC:N confirms this). Signals: POC exploit code is publicly available (VulDB gist) and a vendor patch exists, but there is NO EPSS score, NO CISA KEV listing, and no evidence of active exploitation - E:P (proof-of-concept) is the only exploit-maturity signal. Note a description/code discrepancy: the description names DecodePlainMmMessage in src/lib/nas/encode.cpp, while the published patch touches src/gnb/ngap/nas.cpp (extractSliceInfoAndModifyPdu, which calls DecodeNasMessage) - the crash surfaces in the NAS decode chain invoked from the gNB's NGAP handling; verify exact call path with vendor. Net: publicly-available PoC for a DoS in a niche 5G test tool - a patch-when-convenient issue, not an emergency.

Exploit ScenarioDerived

A malicious or malformed UE sends an Initial (plain, unprotected) NAS Registration Request to the gNB containing a NAS message type or IEI that UERANSIM's decoder does not model. When the gNB decodes the PDU during AMF selection, DecodeNasMessage throws an exception that no handler catches, terminating the gNB process and dropping all attached UEs. Publicly available proof-of-concept exploit code exists (VulDB gist).

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 28, 2026

An uncaught exception in the NAS message decoder of aligungr UERANSIM's gNB component (nr-gnb, versions up to and including 3.3.0) lets a remote, unauthenticated sender crash the simulated 5G base station by delivering a malformed plain Initial NAS message during AMF slice selection, causing the gNB process to terminate. Availability-only impact: no confidentiality or integrity effect, and exploitation is limited to UERANSIM lab/test deployments. Publicly available exploit code exists (a PoC gist is referenced), but there is no indication of confirmed active exploitation, and an upstream fix commit is available.

RemediationAI

Apply the upstream fix commit 1ae9bf2062b57595dbcbc4bc1d0a0ccf06815bac to src/gnb/ngap/nas.cpp (and the accompanying ngap changes) or upgrade to a build that includes it - this is an upstream fix available as a PR/commit, and a released patched version has not been independently confirmed, so pin the commit or cherry-pick it into your build. Advisory and PoC context are at https://vuldb.com/vuln/410903 and https://gist.github.com/centauruszzz/f729edf89aa32ae3cfe4865c71ad1102. Because only unprotected Initial NAS messages reach the throwing decoder, there is no application-level feature to simply disable without breaking 5G registration; instead, restrict network and radio reachability to the gNB's NGAP/SCTP endpoint (commonly port 38412) and to trusted UEs where the deployment permits, accepting that a real UE must still reach the gNB and that this control only helps in closed lab topologies. Run nr-gnb under a process supervisor (for example systemd with Restart=always) so a crash is recovered automatically, with the trade-off that all in-flight UE contexts and registrations are lost on restart. Isolate simulator nodes on segmented VLANs or containers so a crash cannot affect adjacent infrastructure, and treat the gNB as untrusted-facing until patched. The same commit also fixes a UE context leak and a NAS IE re-encoding issue, so applying it improves stability beyond this CVE. No vendor-released patch version number is specified in the available data; do not assume any particular tagged release is fixed without verifying the commit is present.

Affected VersionsENISA

UERANSIM 3.3.0
UERANSIM 3.0
UERANSIM 3.1
UERANSIM 3.2

Affected Packages

euvd ueransim no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

UERANSIM is an open-source 5G System simulator implementing both a UE and a gNB (RAN), speaking 3GPP NGAP over SCTP to an AMF and 3GPP NAS between UE and core. When the gNB receives an InitialUEMessage carrying an Initial NAS PDU, NgapTask calls into the NAS codec (DecodeNasMessage, with the plain mobility-management path through src/lib/nas/encode.cpp / DecodePlainMmMessage) to read the requested NSSAI and pick a suitable AMF. The root cause is CWE-248 (Uncaught Exception): the decoder throws a std::exception when it encounters a message type or IEI it does not model, and because NtsTask runs its onLoop on a bare thread with no surrounding try/catch, the exception escapes and terminates the gNB process. The upstream fix wraps that decode in a try/catch (logging and forwarding the PDU untouched instead), additionally short-circuits any NAS PDU carrying a security header so it is never decoded for AMF selection, and cleans up a UE context leak. The vulnerable path is reachable only via unprotected (NOT_PROTECTED) Initial NAS messages, since Initial Registration precedes NAS security establishment; protected messages pass through without decoding.

Know when Ueransim gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 7.5 HIGH

Unauthenticated remote UE sends a crafted plain NAS message (PR:N/AC:L); uncaught exception terminates the whole gNB process, so A:H (higher than vendor VA:L), with no C/I impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
CVSS changed
Sep 28, 2026 - 10:22 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
CVE Published
Sep 28, 2026 - 09:30 cve.org
MEDIUM 6.9

DescriptionCVE.org

A flaw has been found in aligungr UERANSIM up to 3.3.0. This affects the function DecodePlainMmMessage in the library src/lib/nas/encode.cpp of the component nr-gnb. Executing a manipulation can lead to uncaught exception. The attack can be launched remotely. The exploit has been published and may be used. This patch is called 1ae9bf2062b57595dbcbc4bc1d0a0ccf06815bac. It is best practice to apply a patch to resolve this issue.

Threat Intelligence Overview

EPSS Score
0.5%
Top 57% exploitable
Prevalence
Low
open-source 5G UE/gNB simulator used mainly in labs and research
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy