{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69252 is a medium-severity vulnerability in free5gc udm, published on 23 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-69252 and fix it if it is affected.\n\nWhat it is: CVE-2025-69252 is a medium-severity vulnerability in free5gc udm, published on 23 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-69252 in the wild and no public exploit code.\n\nAffected product: free5gc udm. 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-69252/ (Markdown: https://insights.sbomify.com/CVE-2025-69252/index.md)","id":"CVE-2025-69252","markdown":"https://insights.sbomify.com/CVE-2025-69252/index.md","name":"CVE-2025-69252","record":{"aliases":["GHSA-v8cv-qvf6-9rpm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G core network","requires_auth":"none","summary":"Remote unauthenticated attackers can crash the free5GC UDM service via a crafted PUT request, causing a denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"udm","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:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"free5gc UDM provides Unified Data Management (UDM) for free5GC, an open-source project for 5th generation (5G) mobile core networks. Versions up to and including 1.4.1 have a NULL Pointer Dereference vulnerability. Remote unauthenticated attackers can trigger a service panic (Denial of Service) by sending a crafted PUT request with an unexpected ueId, crashing the UDM service. All deployments of free5GC using the UDM component may be affected. free5gc/udm pull request 76 contains a fix for the issue. 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 has Null Pointer Dereference in UDM, Leading to Service Panic","id":"CVE-2025-69252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"free5GC vulnerable to improper error handling in NEF with information exposure","id":"CVE-2025-69253"},"packages":[],"prev":{"headline":"free5GC has Improper Input Validation in UDM, Leading to Information Exposure","id":"CVE-2025-69251"},"products":["udm"],"published":"2026-02-23","related":[{"cvss_score":8.7,"headline":"free5GC UDM DataChangeNotification Procedure Panic Due to Nil Pointer Dereference","id":"CVE-2026-33064","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.7,"headline":"free5GC UDM vulnerable to null byte injection in URL path parameters causing 500 Internal Server Error","id":"CVE-2026-33191","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.7,"headline":"free5GC UDM incorrectly returns 500 for empty supi path parameter in PATCH sdm-subscriptions reques","id":"CVE-2026-33192","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.5,"headline":"free5GC udm vulnerable to Invalid Curve Attack","id":"CVE-2023-46324","kev_date_added":null,"published":"2023-10-23"},{"cvss_score":6.9,"headline":"free5GC UDM incorrectly returns 500 for empty supi path parameter in DELETE sdm-subscriptions request","id":"CVE-2026-33065","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":6.6,"headline":"free5GC has Improper Input Validation in UDM UEAU Service","id":"CVE-2026-27642","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":6.6,"headline":"free5GC has Improper Error Handling in UDM, Leading to Information Exposure","id":"CVE-2025-69250","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-25","vendors":["free5gc"]},"summary":"Remote unauthenticated attackers can crash the free5GC UDM service via a crafted PUT request, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-69252/"}