CVE-2026-101035

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-28. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 28, 2026

Advisory Details (3)

Auto-updated Sep 28, 2026
🔬 Proof of concept available. Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

GitHub - aligungr/UERANSIM: Open source 5G UE and RAN (gNodeB) implementation. · GitHub

https://github.com/aligungr/UERANSIM/
github_commit

commit 1ae9bf2062b5 (aligungr/UERANSIM)

Fix landed in aligungr/UERANSIM commit 1ae9bf2062b5 — awaiting tagged release

https://github.com/aligungr/UERANSIM/commit/1ae9bf2062b57595dbcbc4bc1d0a0ccf06815bac
generic🟡 PoC Available

UERANSIM_3.md · GitHub

https://gist.github.com/centauruszzz/f729edf89aa32ae3cfe4865c71ad1102

Vendor Advisories for CVE-2026-101035(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 24× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-03 19:16 UTCEG score recompute
  2. 2026-10-03 19:16 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-02 18:30 UTCEG score recompute
  5. 2026-10-02 18:30 UTCGHSA enrichment
  6. 2026-10-01 19:49 UTCEPSS rescore
  7. 2026-10-01 17:45 UTCGHSA enrichment
  8. 2026-09-30 17:00 UTCEG score recompute
  9. 2026-09-30 17:00 UTCGHSA enrichment
  10. 2026-09-30 15:02 UTCEPSS rescore
  11. 2026-09-29 16:14 UTCEG score recompute
  12. 2026-09-29 16:14 UTCGHSA enrichment
  13. 2026-09-29 15:20 UTCEPSS rescore
  14. 2026-09-28 15:28 UTCEG score recompute
  15. 2026-09-28 15:28 UTCGHSA enrichment
  16. 2026-09-28 13:50 UTCEPSS rescore
  17. 2026-09-28 11:29 UTCEG score recompute
  18. 2026-09-28 11:29 UTCNVD updateCVSS v4 → 5.5
  19. 2026-09-28 11:03 UTCEG score recompute
  20. 2026-09-28 11:02 UTCMITRE cvelistV5CVSS v4 → 6.9
  21. 2026-09-28 10:38 UTCEG score recompute
  22. 2026-09-28 10:34 UTCNVD updateCVSS v4 → 5.5
  23. 2026-09-28 09:42 UTCEG score recompute
  24. 2026-09-28 09:42 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-101035?
CVE-2026-101035 is a medium vulnerability published on September 28, 2026. 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…
When was CVE-2026-101035 disclosed?
CVE-2026-101035 was first published on September 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-101035 actively exploited?
CVE-2026-101035 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101035?
CVE-2026-101035 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101035?
An upstream fix for CVE-2026-101035 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-101035 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-101035

Explore →

Is Your Infrastructure Affected by CVE-2026-101035?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs