# CVE-2025-69253: free5GC vulnerable to improper error handling in NEF with information exposure

> Remote attackers can obtain internal error details from the NEF component, aiding service fingerprinting in free5GC deployments.

- **Severity:** Medium 6.6 (`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/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-cj2h-x8qm-xgwc

## What is CVE-2025-69253?

CVE-2025-69253 is a medium-severity vulnerability in free5gc udr, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

free5GC is an open-source project for 5th generation (5G) mobile core networks. Versions up to and including 1.4.1 of the User Data Repository are affected by Improper Error Handling with Information Exposure. 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 vulnerable. free5gc/udr pull request 56 contains a patch. No direct workaround is available at the application level. Applying the official patch is recommended.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2025-69253?

It affects 1 product.


Products: Free5gc Udr.

## How do I fix CVE-2025-69253?

No fix has been published for CVE-2025-69253 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-69253 being exploited?

There is no known exploitation of CVE-2025-69253 in the wild and no public exploit code.

## Other vulnerabilities in free5gc udr

- [CVE-2026-27643](https://insights.sbomify.com/CVE-2026-27643/): free5GC has improper error handling in NEF with information exposure (medium 6.6)
- [CVE-2025-69208](https://insights.sbomify.com/CVE-2025-69208/): free5GC UDR's NEF incorrectly returns 500 for missing PFD data (UDR 404) in Nnef_PfdManagement GET request (low 2.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-69253 and fix it if it is affected.

What it is: CVE-2025-69253 is a medium-severity vulnerability in free5gc udr, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-69253 in the wild and no public exploit code.

Affected product: free5gc udr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-69253/ (Markdown: https://insights.sbomify.com/CVE-2025-69253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-69253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-69253
- OSV: https://osv.dev/vulnerability/CVE-2025-69253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-69253/
Summaries are generated and may contain mistakes; the official description above is the record.