CVE-2026-40248: Github.com/free5gc/udr Free5gc UDR Improper Path Validation Vulnerability

HIGH
Advisory Identifier: GHSA-jgq2-qv8v-5cmj
CVSS 7.5
CWE-285 CWE-636
Published
Advisory Summary

CVE-2026-40248 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 creation and modification of traffic influence subscriptions. Remediation is available in the latest vendor maintenance releases.

CVE-2026-40248 at a Glance

CVE Identifier CVE-2026-40248
GHSA Identifier GHSA-jgq2-qv8v-5cmj
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-285: Improper Authorization
Affected Product Github.com/free5gc/udr
Package Ecosystem Go
Published Date
Last Updated

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:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-40248

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.

github.com/free5gc/udr fixed: Latest secure release
Upgrade github.com/free5gc/udr to Latest secure release
Verify Direct and Transitive Dependencies

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-40248, 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

### Summary An improper path validation vulnerability in the UDR service allows any unauthenticated attacker with access to the 5G Service Based Interface (SBI) to create or overwrite Traffic Influence Subscriptions by supplying an arbitrary value in place of the expected `subs-to-notify` path segment. ### Details The endpoint `PUT /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`. In 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: 1. The function `HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdPut`in `./free5gc_4-2-1/free5gc/NFs/udr/internal/sbi/api_datarepository.go`checks whether `influenceId != "subs-to-notify"`. 2. If the value is different, it calls `c.String(http.StatusNotFound, "404 page not found")`, **but it does not return afterwards**. 3. Execution continues, the request body is still parsed, and the handler calls `s.Processor().ApplicationDataInfluenceDataSubsToNotifySubscriptionIdPutProcedure(c, subscriptionId, &trafficInfluSub)`. 4. The processor creates or updates the subscription identified by `subscriptionId` even though the path is invalid and the request should have been rejected. As a result, an attacker can send a request to an invalid path, receive an apparent `404 page not found` response, and still successfully create or modify the target subscription in the UDR. The missing `return` after sending the 404 response in `api_datarepository.go` is the root cause of this vulnerability. ### PoC No authentication is required. The attacker can choose an arbitrary `subscriptionId`. ```bash curl -v -X PUT "http://<udr-host>/nudr-dr/v2/application-data/influenceData/WRONGID/nuovoid" \ -H "Content-Type: application/json" \ -d '{ "notificationUri":"http://evil.com", "dnns":["internet"], "supis":["imsi-999999999999999"] }' ``` Response: ``` HTTP/1.1 404 Not Found 404 page not found{"dnns":["internet"],"supis":["imsi-999999999999999"],"notificationUri":"http://evil.com"} ``` Now verify that the object was actually written: ```bash curl -v "http://<udr-host>/nudr-dr/v2/application-data/influenceData/subs-to-notify/nuovoid" ``` Response: ```json {"dnns":["internet"],"supis":["imsi-999999999999999"],"notificationUri":"http://evil.com"} ``` ### Impact This is an unauthenticated unauthorized write vulnerability. Any attacker with network access to the SBI can create or overwrite Traffic Influence Subscriptions by choosing an arbitrary subscriptionId, even when using an invalid path that should have been rejected. This allows injection of attacker-controlled subscription data, including arbitrary SUPIs and attacker-controlled notificationUri values. Depending on deployment behavior, this may enable malicious redirection of policy-related notifications, corruption of subscription state, or disruption of legitimate network policy logic. The attack is also difficult to detect because the API returns a misleading 404 Not Found response even when the write operation is actually performed. Impacted deployments: any free5GC instance where the SBI is reachable by untrusted parties (e.g., misconfigured network segmentation, rogue NF, or compromised internal host). ### Patch The vulnerability has been confirmed patched by adding the missing return statement in NFs/udr/internal/sbi/api_datarepository.go, function HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdPut: ```go if influenceId != "subs-to-notify" { c.String(http.StatusNotFound, "404 page not found") return } ``` With the patch applied, requests using an invalid influenceId now correctly return HTTP 404 and do not create or modify subscription data.

CVE-2026-40248 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-40248?
CVE-2026-40248 is a security vulnerability in Github.com/free5gc/udr involving free5gc UDR improper path validation allows unauthenticated creation and modification of Traffic Influence Subscriptions under CWE-285: Improper Authorization.
Which Github.com/free5gc/udr versions are affected?
Affected versions include releases prior to current release patches across affected packages: github.com/free5gc/udr.
What version fixes CVE-2026-40248?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/free5gc/udr affected?
Yes, github.com/free5gc/udr is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2026-40248?
CVE-2026-40248 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-40248?
CVE-2026-40248 is classified under CWE-285: Improper Authorization (The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.).
How can I check Go dependencies for CVE-2026-40248?
Run the dependency tree command: 'inspect dependencies for github.com/free5gc/udr'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-jgq2-qv8v-5cmj",
  "modified" : "2026-04-24T20:36:00Z",
  "published" : "2026-04-14T20:00:45Z",
  "aliases" : [ "CVE-2026-40248" ],
  "summary" : "free5gc UDR improper path validation allows unauthenticated creation and modification of 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 create or overwrite Traffic Influence Subscriptions by supplying an arbitrary value in place of the expected `subs-to-notify` path segment.\n\n### Details\nThe endpoint `PUT /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 `HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdPut`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, the request body is still parsed, and the handler calls `s.Processor().ApplicationDataInfluenceDataSubsToNotifySubscriptionIdPutProcedure(c, subscriptionId, &trafficInfluSub)`.\n4. The processor creates or updates 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 successfully create or modify the target subscription in the UDR.\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. The attacker can choose an arbitrary `subscriptionId`.\n\n```bash\ncurl -v -X PUT \"http://<udr-host>/nudr-dr/v2/application-data/influenceData/WRONGID/nuovoid\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"notificationUri\":\"http://evil.com\",\n    \"dnns\":[\"internet\"],\n    \"supis\":[\"imsi-999999999999999\"]\n  }'\n```\n\nResponse:\n```\nHTTP/1.1 404 Not Found\n404 page not found{\"dnns\":[\"internet\"],\"supis\":[\"imsi-999999999999999\"],\"notificationUri\":\"http://evil.com\"}\n```\nNow verify that the object was actually written:\n\n```bash\ncurl -v \"http://<udr-host>/nudr-dr/v2/application-data/influenceData/subs-to-notify/nuovoid\"\n```\nResponse:\n```json\n{\"dnns\":[\"internet\"],\"supis\":[\"imsi-999999999999999\"],\"notificationUri\":\"http://evil.com\"}\n```\n### Impact\nThis is an unauthenticated unauthorized write vulnerability. Any attacker with network access to the SBI can create or overwrite Traffic Influence Subscriptions by choosing an arbitrary subscriptionId, even when using an invalid path that should have been rejected.\n\nThis allows injection of attacker-controlled subscription data, including arbitrary SUPIs and attacker-controlled notificationUri values. Depending on deployment behavior, this may enable malicious redirection of policy-related notifications, corruption of subscription state, or disruption of legitimate network policy logic.\n\nThe attack is also difficult to detect because the API returns a misleading 404 Not Found response even when the write operation is actually performed.\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 HandleApplicationDataInfluenceDataSubsToNotifySubscriptionIdPut:\n\n```go\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 create or modify subscription data.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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-jgq2-qv8v-5cmj"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40248"
  }, {
    "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:45Z",
    "nvd_published_at" : "2026-04-16T22:16:38Z"
  }
}