{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-69232 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69232 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69232 is a low-severity denial of service 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-69232 and fix it if it is affected.\n\nWhat it is: CVE-2025-69232 is a low-severity denial of service 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-69232 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-69232/ (Markdown: https://insights.sbomify.com/CVE-2025-69232/index.md)","id":"CVE-2025-69232","markdown":"https://insights.sbomify.com/CVE-2025-69232/index.md","name":"CVE-2025-69232","record":{"aliases":["GHSA-8m42-qw58-8362"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G core network software","requires_auth":"none","summary":"Remote attackers can disrupt 5G core network services by sending malformed PFCP requests to the UPF, causing SMF reconnection loops.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"go-upf","vendor":"free5gc"},{"product":"smf","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-20","name":"Improper Input Validation"}],"description":"free5GC is an open-source project for 5th generation (5G) mobile core networks. free5GC go-upf versions up to and including 1.2.6, corresponding to free5gc smf up to and including 1.4.0, have an Improper Input Validation and Protocol Compliance vulnerability leading to Denial of Service. Remote attackers can disrupt core network functionality by sending a malformed PFCP Association Setup Request. The UPF incorrectly accepts it, entering an inconsistent state that causes subsequent legitimate requests to trigger SMF reconnection loops and service degradation. All deployments of free5GC using the UPF and SMF components may be affected. As of time of publication, a fix is in development but not yet available. No direct workaround is available at the application level. Applying the official patch, once released, 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 hasProtocol Compliance Violation in UPF Leading to SMF Service Disruption","id":"CVE-2025-69232","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Apache CloudStack: Domain/account resources limits not honored","id":"CVE-2025-69233"},"packages":[],"prev":{"headline":"OpenEMR has a Stored XSS in GAD-7 Form that Enables Session Hijacking and Privilege Escalation","id":"CVE-2025-69231"},"products":["go-upf","smf"],"published":"2026-02-23","related":[{"cvss_score":2.7,"headline":"free5GC has Heap Buffer Overflow in UPF Leading to Denial of Service","id":"CVE-2025-69247","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 disrupt 5G core network services by sending malformed PFCP requests to the UPF, causing SMF reconnection loops.","url":"https://insights.sbomify.com/CVE-2025-69232/"}