Is there a public PoC exploit available for CVE-2026-7708?

Yes, a public proof-of-concept exploit is available for CVE-2026-7708. Prioritise patching immediately. EPSS: 0.0%.

Open5GS CVE-2026-7708

Q: What is the CVSS score of CVE-2026-7708?

CVE-2026-7708 has a CVSS 4.0 base score of 2.1 (Low). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

LOW

Improper Resource Shutdown or Release (CWE-404)

2026-05-03 VulDB

Denial Of Service Open5gs

2.1

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

2.1 LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

May 03, 2026 - 23:30 vuln.today

Severity Changed

May 03, 2026 - 23:22 NVD

MEDIUM LOW

CVSS changed

May 03, 2026 - 23:22 NVD

4.3 (MEDIUM) 2.1 (LOW)

PoC Detected

May 03, 2026 - 23:16 vuln.today

Public exploit code

Analysis Generated

May 03, 2026 - 23:00 vuln.today

CVE Published

May 03, 2026 - 22:45 nvd

LOW 2.1

DescriptionCVE.org

A vulnerability was determined in Open5GS up to 2.7.7. The affected element is the function ogs_dbi_subscription_data in the library /lib/dbi/subscription.c of the component UDR. This manipulation of the argument supi_id causes denial of service. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. The project was informed of the problem early through an issue report but has not responded yet.

AnalysisAI

Denial of service in Open5GS UDR component up to version 2.7.7 allows authenticated remote attackers to crash the subscription data service by manipulating the supi_id argument to the ogs_dbi_subscription_data function. Publicly available exploit code exists, and the vendor has been notified via issue report but has not yet released a patch.

Technical ContextAI

Open5GS is an open-source implementation of 3GPP core network elements. The vulnerability resides in the User Data Repository (UDR) component, specifically in the ogs_dbi_subscription_data function within /lib/dbi/subscription.c. This function handles subscription data queries and accepts a supi_id (Subscription Permanent Identifier) parameter. The issue stems from improper argument validation (CWE-404: Improper Resource Validation), where malformed or unexpected supi_id values are not adequately sanitized before database operations, leading to resource exhaustion or service termination. The UDR is a critical network element in 5G core networks responsible for storing and retrieving subscriber information, making denial of service against it operationally significant.

RemediationAI

No vendor-released patch has been identified at time of analysis. The project maintainers were informed via issue report (https://github.com/open5gs/open5gs/issues/4412) but have not responded with a fix. Immediate remediation options include: (1) Upgrade to a version later than 2.7.7 once a patched release is available, monitoring the Open5GS GitHub repository for updates. (2) Implement network-level access controls to restrict authenticated access to the UDR interface-limit connections to the UDR service (typically listening on port 7777 for HTTP/REST APIs) to trusted signaling network elements only, reducing the pool of users who can authenticate to the service. (3) Deploy input validation at the network gateway or API gateway layer to sanitize supi_id parameters before they reach the UDR, rejecting malformed or suspicious identifiers. (4) Implement rate limiting and connection throttling on the UDR to mitigate repeated exploitation attempts, with the trade-off that legitimate bursts of subscriber queries may be delayed. Monitor UDR service availability and resource consumption to detect active exploitation.