{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69247 is a low-severity memory corruption vulnerability in free5gc go-upf, 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-69247 and fix it if it is affected.\n\nWhat it is: CVE-2025-69247 is a low-severity memory corruption vulnerability in free5gc go-upf, 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-69247 in the wild and no public exploit code.\n\nAffected product: free5gc go-upf. 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-69247/ (Markdown: https://insights.sbomify.com/CVE-2025-69247/index.md)","id":"CVE-2025-69247","markdown":"https://insights.sbomify.com/CVE-2025-69247/index.md","name":"CVE-2025-69247","record":{"aliases":["GHSA-gf69-93xr-p23g"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G Core Network","requires_auth":"none","summary":"Remote attackers can crash the free5GC UPF component via crafted PFCP requests, causing service disruption for connected users.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"go-upf","vendor":"free5gc"}],"cvss":{"score":2.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"free5GC go-upf is the User Plane Function (UPF) implementation for 5G networks that is part of the free5GC project. Versions prior to 1.2.8 have a Heap-based Buffer Overflow (CWE-122) vulnerability leading to Denial of Service. Remote attackers can crash the UPF network element by sending a specially crafted PFCP Session Modification Request with an invalid SDF Filter length field. This causes a heap buffer overflow, resulting in complete service disruption for all connected UEs and potential cascading failures affecting the SMF. All deployments of free5GC using the UPF component may be affected. Version 1.2.8 of go-upf contains a fix.","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 Heap Buffer Overflow in UPF Leading to Denial of Service","id":"CVE-2025-69247","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 Array Index Out of Bounds in AMF Leading to Denial of Service","id":"CVE-2025-69248"},"packages":[],"prev":{"headline":"Lack of bruteforce protection in Raytha CMS","id":"CVE-2025-69246"},"products":["go-upf"],"published":"2026-02-23","related":[{"cvss_score":2.7,"headline":"free5GC hasProtocol Compliance Violation in UPF Leading to SMF Service Disruption","id":"CVE-2025-69232","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 attackers can crash the free5GC UPF component via crafted PFCP requests, causing service disruption for connected users.","url":"https://insights.sbomify.com/CVE-2025-69247/"}