CVE-2026-40249
Fail-Open Logic Flaw in free5GC UDR Policy Data Update
Publication date: 2026-04-16
Last updated on: 2026-04-16
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| free5gc | udr_service | to 4.2.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-754 | The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. |
| CWE-636 | When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in free5GC, an open-source 5G core network implementation, specifically in versions 4.2.1 and below of the UDR service. The issue occurs in the PUT handler for updating Policy Data notification subscriptions at the endpoint /nudr-dr/v2/policy-data/subs-to-notify/{subsId}. When there are errors in retrieving or deserializing the request body, the handler sends HTTP 400 or 500 error responses but does not stop execution. Instead, it continues processing with a potentially uninitialized or partially initialized PolicyDataSubscription object.
This fail-open behavior means that despite the error, the system may unintentionally modify existing Policy Data notification subscriptions using invalid or empty input, depending on how downstream processors and storage handle the data.
How can this vulnerability impact me? :
The vulnerability can lead to unintended modifications of Policy Data notification subscriptions within the free5GC UDR service. Because the system continues processing after errors with potentially invalid or empty data, it may corrupt or alter subscription data incorrectly.
This could result in incorrect policy enforcement or notification behavior in the 5G core network, potentially affecting network operations or service quality.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability exists in free5GC UDR service versions 4.2.1 and below, where the PUT handler for updating Policy Data notification subscriptions does not properly stop execution after request body errors, potentially allowing unintended modifications.
Since a patched version was not available at the time of publication, immediate mitigation steps include:
- Restrict access to the vulnerable PUT endpoint (/nudr-dr/v2/policy-data/subs-to-notify/{subsId}) to trusted sources only.
- Implement additional input validation or filtering at a network or application firewall level to block malformed or invalid requests targeting this endpoint.
- Monitor logs for unusual or repeated 400 or 500 HTTP responses from this endpoint, which may indicate exploitation attempts.
- Plan to upgrade to a patched version once it becomes available.