How severe is GHSA-5rvc-5cwx-g5x8?

No CVSS score has been assigned to GHSA-5rvc-5cwx-g5x8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-5rvc-5cwx-g5x8?

GHSA-5rvc-5cwx-g5x8 affects the following packages: github.com/free5gc/udm (Go). Ecosystems affected: Go.

How do I fix GHSA-5rvc-5cwx-g5x8?

Update github.com/free5gc/udm to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5rvc-5cwx-g5x8 is resolved across your whole dependency graph.

How do I detect GHSA-5rvc-5cwx-g5x8 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/udm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-5rvc-5cwx-g5x8 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-5rvc-5cwx-g5x8?

O3 pinpoints whether GHSA-5rvc-5cwx-g5x8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-5rvc-5cwx-g5x8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5rvc-5cwx-g5x8 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-5rvc-5cwx-g5x8?

GHSA-5rvc-5cwx-g5x8 is classified as CWE-209 (CWE-209). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5rvc-5cwx-g5x8 published, and has it been updated?

GHSA-5rvc-5cwx-g5x8 was published on March 18, 2026 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-5rvc-5cwx-g5x8

Fix: free5gc/udm#79

GHSA-5rvc-5cwx-g5x8 is a CWE-209 vulnerability in github.com/free5gc/udm. O3 Security confirms whether GHSA-5rvc-5cwx-g5x8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

free5GC UDM incorrectly returns 500 for empty supi path parameter in PATCH sdm-subscriptions reques

Also known asCVE-2026-33192GO-2026-4755

Published

Mar 18, 2026

Updated

Mar 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐹github.com/free5gc/udm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact
This is an Improper Error Handling vulnerability with Information Exposure implications, combined with an HTTP Method Translation issue.

Security Impact: The UDM incorrectly converts a downstream 400 Bad Request (from UDR) into a 500 Internal Server Error when handling PATCH requests with an empty supi path parameter. Additionally, the UDM incorrectly translates the PATCH method to PUT when forwarding to UDR, indicating a deeper architectural issue. This leaks internal error handling behavior and makes it difficult for clients to distinguish between client-side errors and server-side failures.
Functional Impact: When a client sends a PATCH request with an empty supi (e.g., double slashes // in URL path), the UDM forwards a PUT request to UDR with the malformed path, which correctly returns 400. However, UDM propagates this as 500 SYSTEM_FAILURE instead of returning the appropriate 400 error to the client. This violates REST API best practices for PATCH operations and may indicate improper HTTP method handling.
Affected Parties: All deployments of free5GC v4.0.1 using the UDM Nudm_SDM service with PATCH operations on sdm-subscriptions endpoint.

Patches
Yes, the issue has been patched.
The fix is implemented in PR free5gc/udm#79.
Users should upgrade to the next release of free5GC that includes this commit.

Workarounds
There is no direct workaround at the application level. The recommendation is to apply the provided patch or implement API gateway-level validation to reject PATCH requests with empty path parameters before they reach UDM.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/free5gc/udm`	all versions	1.4.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/free5gc/udm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/free5gc/udm to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5rvc-5cwx-g5x8 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-5rvc-5cwx-g5x8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-5rvc-5cwx-g5x8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Impact** This is an Improper Error Handling vulnerability with Information Exposure implications, combined with an HTTP Method Translation issue. - **Security Impact**: The UDM incorrectly converts a downstream 400 Bad Request (from UDR) into a 500 Internal Server Error when handling PATCH requests with an empty `supi` path parameter. Additionally, the UDM incorrectly translates the PATCH method to PUT when forwarding to UDR, indicating a deeper architectural issue. This leaks internal error handling behavior and makes it difficult for clients to distinguish between client-side errors an

O3 Security · Impact-Aware SCA

Is GHSA-5rvc-5cwx-g5x8 in your dependencies?

O3 detects GHSA-5rvc-5cwx-g5x8 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works