{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69253 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69253 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-69253 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-69253 in the wild and no public exploit code.\n\nAffected product: free5gc udr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69253/ (Markdown: https://insights.sbomify.com/CVE-2025-69253/index.md)","id":"CVE-2025-69253","markdown":"https://insights.sbomify.com/CVE-2025-69253/index.md","name":"CVE-2025-69253","record":{"aliases":["GHSA-cj2h-x8qm-xgwc"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"5G core network software","requires_auth":"none","summary":"Remote attackers can obtain internal error details from the NEF component, aiding service fingerprinting in free5GC deployments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"udr","vendor":"free5gc"}],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"free5GC vulnerable to improper error handling in NEF with information exposure","id":"CVE-2025-69253","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"RustFS gRPC GetMetrics deserialization panic enables remote DoS","id":"CVE-2025-69255"},"packages":[],"prev":{"headline":"free5GC has Null Pointer Dereference in UDM, Leading to Service Panic","id":"CVE-2025-69252"},"products":["udr"],"published":"2026-02-24","related":[{"cvss_score":6.6,"headline":"free5GC has improper error handling in NEF with information exposure","id":"CVE-2026-27643","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":2.7,"headline":"free5GC UDR's NEF incorrectly returns 500 for missing PFD data (UDR 404) in Nnef_PfdManagement GET request","id":"CVE-2025-69208","kev_date_added":null,"published":"2026-02-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["free5gc"]},"summary":"Remote attackers can obtain internal error details from the NEF component, aiding service fingerprinting in free5GC deployments.","url":"https://insights.sbomify.com/CVE-2025-69253/"}