CVE-2026-47780

MEDIUMPre-NVD 6.96.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this weekElevated
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

free5GC is an open-source implementation of the 5G core network. In 4.2.3 and earlier, HandleCreateEeSubscriptions and HandleQueryeesubscriptions in free5gc/udr internal/sbi/api_datarepository.go validate the ueId path value with a regular expression whose final .+ alternative accepts every non-empty string instead of restricting identifiers to supported SUPI and GPSI formats. An actor with network reachability to the UDR SBI can submit a non-3GPP identifier to /nudr-dr/v2/subscription-data/{ueId}/context-data/ee-subscriptions, causing the identifier to pass validation and enter the normal create or query flow. The advisory does not independently establish whether authentication is required. Invalid identifiers can be persisted and retrieved as subscription records, enabling unauthorized data creation, UDR namespace pollution, persistent subscriber-metadata corruption, and interference with downstream components that trust stored identifiers to use valid 3GPP formats. The exposure is most relevant in lab, test, or loosely segmented service-based-interface deployments where direct UDR access is possible.

CVSS v3
6.9
EG Score
6.9(low)
EG Risk
62(Attend)
EG Risk 62/100SSVC: Attend

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
Severity69% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 11, 2026

Last Modified

September 15, 2026

Advisory Details (1)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

UDR Improper ueId validation in free5GC EE subscription handlers allows arbitrary identifier persistence · Advisory · free5gc/free5gc · GitHub

https://github.com/free5gc/free5gc/security/advisories/GHSA-6gxq-gpr8-xgjp

Vendor Advisories for CVE-2026-47780(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
gogithub.com/free5gc/udr—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/free5gc/udr———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 12× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-16 14:08 UTCEPSS rescore
  3. 2026-09-15 16:36 UTCEG score recompute
  4. 2026-09-15 16:36 UTCGHSA enrichment
  5. 2026-09-15 15:35 UTCEG score recompute
  6. 2026-09-15 15:35 UTCGHSA enrichment
  7. 2026-09-15 14:53 UTCEG score recompute▲ 6.90
  8. 2026-09-15 14:53 UTCGHSA enrichment
  9. 2026-09-15 14:52 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  10. 2026-09-14 04:10 UTCGHSA enrichment
  11. 2026-08-31 00:05 UTCGHSA enrichment
  12. 2026-08-23 10:43 UTCGHSA enrichment
  13. 2026-08-19 14:54 UTCGHSA enrichment
  14. 2026-08-16 02:07 UTCGHSA enrichment
  15. 2026-08-13 05:34 UTCGHSA enrichment
  16. 2026-08-10 08:58 UTCGHSA enrichment
  17. 2026-08-07 12:24 UTCGHSA enrichment
  18. 2026-08-04 15:51 UTCGHSA enrichment
  19. 2026-08-01 14:01 UTCEG score recompute
  20. 2026-08-01 14:01 UTCGHSA enrichment
  21. 2026-07-29 17:28 UTCGHSA enrichment
  22. 2026-07-26 20:54 UTCEG score recompute
  23. 2026-07-26 20:54 UTCGHSA enrichment
  24. 2026-07-23 03:17 UTCEG score recompute
  25. 2026-07-16 23:29 UTCGHSA enrichment
Show 16 more
  1. 2026-07-13 19:19 UTCGHSA enrichment
  2. 2026-07-10 18:38 UTCGHSA enrichment
  3. 2026-07-07 21:44 UTCGHSA enrichment
  4. 2026-07-04 11:27 UTCGHSA enrichment
  5. 2026-07-01 14:33 UTCGHSA enrichment
  6. 2026-06-28 17:59 UTCGHSA enrichment
  7. 2026-06-25 21:26 UTCGHSA enrichment
  8. 2026-06-23 00:53 UTCGHSA enrichment
  9. 2026-06-20 04:02 UTCGHSA enrichment
  10. 2026-06-17 07:25 UTCGHSA enrichment
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-14 10:29 UTCGHSA enrichment
  13. 2026-06-13 23:00 UTCEPSS rescore
  14. 2026-06-12 23:12 UTCEPSS rescore
  15. 2026-06-11 13:56 UTCEG score recompute
  16. 2026-06-11 13:56 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-47780?
CVE-2026-47780 is a medium vulnerability published on June 11, 2026. free5GC is an open-source implementation of the 5G core network. In 4.2.3 and earlier, HandleCreateEeSubscriptions and HandleQueryeesubscriptions in free5gc/udr internal/sbi/api_datarepository.go validate the ueId path value with a regular expression whose final .+ alternative accepts every…
When was CVE-2026-47780 disclosed?
CVE-2026-47780 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on September 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47780 actively exploited?
CVE-2026-47780 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.5% of all scored CVEs.
What is the CVSS score of CVE-2026-47780?
CVE-2026-47780 has a CVSS v3 base score of 6.9 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-47780?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47780, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47780

Explore →

Is Your Infrastructure Affected by CVE-2026-47780?

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

Start Free Scan →Browse All CVEs