CVE-2026-27643: CWE-209: Generation of Error Message Containing Sensitive Information in free5gc udr
free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, the NEF component reliably leaks internal parsing error details (e.g., invalid character 'n' after top-level value) to remote clients, which can aid attackers in service fingerprinting. All deployments of free5GC using the Nnef_PfdManagement service may be affected. free5gc/udr pull request 56 contains a patch for the issue. There is no direct workaround at the application level. The recommendation is to apply the provided patch.
AI Analysis
Technical Summary
CVE-2026-27643 is a vulnerability classified under CWE-209 (Generation of Error Message Containing Sensitive Information) found in the free5GC project, an open-source 5G core network implementation. The issue resides in the UDR component, which manages user data repositories. Specifically, the NEF (Network Exposure Function) component leaks detailed parsing error messages when processing malformed input in the Nnef_PfdManagement service. For example, if an invalid character such as 'n' appears after a top-level JSON value, the error message returned to the client includes this internal parsing detail. This behavior can be exploited by remote attackers without authentication or user interaction to gather information about the internal workings and data formats of the service, aiding in service fingerprinting and reconnaissance. The vulnerability affects all free5GC UDR versions up to and including 1.4.1. The issue was addressed in a patch submitted as pull request 56 to the free5gc/udr repository. No direct application-level workarounds exist, making patching the primary remediation. The CVSS 4.0 base score is 6.6 (medium), reflecting the vulnerability's network attack vector, no required privileges or user interaction, and high impact on confidentiality due to information disclosure. There are no known exploits in the wild at this time.
Potential Impact
The primary impact of CVE-2026-27643 is information disclosure that can aid attackers in fingerprinting the free5GC UDR service. By revealing internal parsing error details, attackers can better understand the data structures, input validation mechanisms, and potentially identify other weaknesses in the 5G core network implementation. This reconnaissance capability can facilitate subsequent targeted attacks, such as injection attacks or exploitation of other vulnerabilities. For organizations deploying free5GC in production 5G networks, this could lead to compromised confidentiality of subscriber data or disruption of network services if chained with other exploits. Although the vulnerability itself does not directly allow data modification or denial of service, the leakage of sensitive internal information increases the overall attack surface and risk profile of the 5G core infrastructure. Given the critical role of 5G networks in telecommunications, any compromise could have wide-reaching effects on service availability and privacy.
Mitigation Recommendations
The definitive mitigation for CVE-2026-27643 is to apply the patch provided in free5gc/udr pull request 56, which removes or sanitizes the detailed error messages returned by the NEF component during parsing failures. Organizations should upgrade free5GC UDR to a version that includes this patch or backport the fix if maintaining older versions. Since there is no direct application-level workaround, network-level protections can help reduce exposure: restrict access to the Nnef_PfdManagement service to trusted management networks or VPNs, implement strict input validation and filtering at perimeter firewalls or API gateways, and monitor logs for repeated parsing errors that may indicate reconnaissance attempts. Additionally, security teams should conduct regular vulnerability assessments and penetration tests on 5G core components to detect similar information leakage issues. Employing runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block malformed requests targeting the NEF component can also help mitigate exploitation risk.
Affected Countries
United States, China, South Korea, Japan, Germany, France, United Kingdom, India, Brazil, Australia, Canada, Italy, Spain
CVE-2026-27643: CWE-209: Generation of Error Message Containing Sensitive Information in free5gc udr
Description
free5GC UDR is the user data repository (UDR) for free5GC, an an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, the NEF component reliably leaks internal parsing error details (e.g., invalid character 'n' after top-level value) to remote clients, which can aid attackers in service fingerprinting. All deployments of free5GC using the Nnef_PfdManagement service may be affected. free5gc/udr pull request 56 contains a patch for the issue. There is no direct workaround at the application level. The recommendation is to apply the provided patch.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-27643 is a vulnerability classified under CWE-209 (Generation of Error Message Containing Sensitive Information) found in the free5GC project, an open-source 5G core network implementation. The issue resides in the UDR component, which manages user data repositories. Specifically, the NEF (Network Exposure Function) component leaks detailed parsing error messages when processing malformed input in the Nnef_PfdManagement service. For example, if an invalid character such as 'n' appears after a top-level JSON value, the error message returned to the client includes this internal parsing detail. This behavior can be exploited by remote attackers without authentication or user interaction to gather information about the internal workings and data formats of the service, aiding in service fingerprinting and reconnaissance. The vulnerability affects all free5GC UDR versions up to and including 1.4.1. The issue was addressed in a patch submitted as pull request 56 to the free5gc/udr repository. No direct application-level workarounds exist, making patching the primary remediation. The CVSS 4.0 base score is 6.6 (medium), reflecting the vulnerability's network attack vector, no required privileges or user interaction, and high impact on confidentiality due to information disclosure. There are no known exploits in the wild at this time.
Potential Impact
The primary impact of CVE-2026-27643 is information disclosure that can aid attackers in fingerprinting the free5GC UDR service. By revealing internal parsing error details, attackers can better understand the data structures, input validation mechanisms, and potentially identify other weaknesses in the 5G core network implementation. This reconnaissance capability can facilitate subsequent targeted attacks, such as injection attacks or exploitation of other vulnerabilities. For organizations deploying free5GC in production 5G networks, this could lead to compromised confidentiality of subscriber data or disruption of network services if chained with other exploits. Although the vulnerability itself does not directly allow data modification or denial of service, the leakage of sensitive internal information increases the overall attack surface and risk profile of the 5G core infrastructure. Given the critical role of 5G networks in telecommunications, any compromise could have wide-reaching effects on service availability and privacy.
Mitigation Recommendations
The definitive mitigation for CVE-2026-27643 is to apply the patch provided in free5gc/udr pull request 56, which removes or sanitizes the detailed error messages returned by the NEF component during parsing failures. Organizations should upgrade free5GC UDR to a version that includes this patch or backport the fix if maintaining older versions. Since there is no direct application-level workaround, network-level protections can help reduce exposure: restrict access to the Nnef_PfdManagement service to trusted management networks or VPNs, implement strict input validation and filtering at perimeter firewalls or API gateways, and monitor logs for repeated parsing errors that may indicate reconnaissance attempts. Additionally, security teams should conduct regular vulnerability assessments and penetration tests on 5G core components to detect similar information leakage issues. Employing runtime application self-protection (RASP) or web application firewalls (WAF) with custom rules to detect and block malformed requests targeting the NEF component can also help mitigate exploitation risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-02-20T22:02:30.029Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 699cf533be58cf853bf604ef
Added to database: 2/24/2026, 12:47:47 AM
Last enriched: 3/3/2026, 8:40:49 PM
Last updated: 4/10/2026, 9:10:36 AM
Views: 140
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.