Is CVE-2026-47780 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47780 being exploited in the wild.

How severe is CVE-2026-47780?

Medium severity, with a CVSS score of 4, published 15 September 2026.

Which products and versions are affected?

free5GC Udr <= 1.4.3; github.com/free5gc/udr (Go) <= 1.4.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.4.3.

Is there a fix for CVE-2026-47780?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-47780 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-47780?

Check whether you run free5GC Udr or github.com/free5gc/udr (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47780: free5GC UDR improper input validation in EE subscription handlers

Q: Which products and versions are affected?

free5GC Udr <= 1.4.3; github.com/free5gc/udr (Go) <= 1.4.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.4.3.

Q: Is there a fix for CVE-2026-47780?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-47780 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-47780?

Check whether you run free5GC Udr or github.com/free5gc/udr (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47780 · Severity: medium · CVSS 4 · Published 2026-09-15

free5GC UDR is a data repository used in 5G core networks to store subscriber information. A flaw in how it validates user identifiers allows an attacker to inject and store arbitrary, non-standard data into the database. This can lead to persistent data corruption, unauthorized record creation, and potential issues for other network components that rely on accurate subscriber data.

Technologies: free5GC Udr, github.com/free5gc/udr (Go). Vendors: free5GC, Go.

Quick answers

Is CVE-2026-47780 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47780 being exploited in the wild.
How severe is CVE-2026-47780?: Medium severity, with a CVSS score of 4, published 15 September 2026.
Which products and versions are affected?: free5GC Udr <= 1.4.3; github.com/free5gc/udr (Go) <= 1.4.3, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.4.3.
Is there a fix for CVE-2026-47780?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-47780 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-47780?: Check whether you run free5GC Udr or github.com/free5gc/udr (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An improper input validation vulnerability exists in the free5GC UDR EE subscription handlers (HandleCreateEeSubscriptions and HandleQueryeesubscriptions) within api_datarepository.go. The validation logic uses a regular expression for the 'ueId' parameter that contains a trailing catch-all branch (.|.+), effectively matching any non-empty string. An attacker with network access to the UDR Service Based Interface (SBI) can submit requests with arbitrary identifiers that bypass intended 3GPP format restrictions (e.g., IMSI, MSISDN). These identifiers are successfully persisted in the backend database and can be retrieved via GET requests, leading to unauthorized data creation and potential integrity issues for downstream components.

Affected products

free5gc udr <= 1.4.3

Identifiers

CVE-2026-47780
GHSA-6gxq-gpr8-xgjp
GO-2026-5178

Timeline

2026-06-10: disclosed
2026-06-11: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.