{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69248 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69248 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69248 is a medium-severity memory corruption vulnerability in free5gc amf, 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-69248 and fix it if it is affected.\n\nWhat it is: CVE-2025-69248 is a medium-severity memory corruption vulnerability in free5gc amf, 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-69248 in the wild and no public exploit code.\n\nAffected product: free5gc amf. 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-69248/ (Markdown: https://insights.sbomify.com/CVE-2025-69248/index.md)","id":"CVE-2025-69248","markdown":"https://insights.sbomify.com/CVE-2025-69248/index.md","name":"CVE-2025-69248","record":{"aliases":["GHSA-h6xc-8vvf-jcjp"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G core network software","requires_auth":"none","summary":"Remote attackers can crash the free5GC AMF service via malformed NAS requests, causing denial of service for 5G core networks.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"amf","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-129","name":"Improper Validation of Array Index"}],"description":"free5GC is an open-source project for 5th generation (5G) mobile core networks. Versions up to and including 1.4.1 of free5GC's AMF service have a Buffer Overflow vulnerability leading to Denial of Service. Remote unauthenticated attackers can crash the AMF service by sending a specially crafted NAS Registration Request with a malformed 5GS Mobile Identity, causing complete denial of service for the 5G core network. All deployments of free5GC using the AMF component may be affected. Pull request 43 of the free5gc/nas repo contains a fix. 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 Array Index Out of Bounds in AMF Leading to Denial of Service","id":"CVE-2025-69248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"free5GC has Improper Error Handling in UDM, Leading to Information Exposure","id":"CVE-2025-69250"},"packages":[],"prev":{"headline":"free5GC has Heap Buffer Overflow in UPF Leading to Denial of Service","id":"CVE-2025-69247"},"products":["amf"],"published":"2026-02-23","related":[{"cvss_score":5.5,"headline":"free5GC AMF missing default case in Content-Type switch in HTTPUEContextTransfer","id":"CVE-2026-41136","kev_date_added":null,"published":"2026-04-21"}],"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 attackers can crash the free5GC AMF service via malformed NAS requests, causing denial of service for 5G core networks.","url":"https://insights.sbomify.com/CVE-2025-69248/"}