{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-26025 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-26025 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-26025 is a medium-severity vulnerability in free5gc smf, 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-2026-26025 and fix it if it is affected.\n\nWhat it is: CVE-2026-26025 is a medium-severity vulnerability in free5gc smf, 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-2026-26025 in the wild and no public exploit code.\n\nAffected product: free5gc smf. 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-2026-26025/ (Markdown: https://insights.sbomify.com/CVE-2026-26025/index.md)","id":"CVE-2026-26025","markdown":"https://insights.sbomify.com/CVE-2026-26025/index.md","name":"CVE-2026-26025","record":{"aliases":["GHSA-vw8r-p7h3-g3xh"],"analysis":{"component_type":"server_software","fix_type":"workaround","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G core network","requires_auth":"none","summary":"Attackers can crash the free5GC SMF by sending malformed PFCP messages, causing denial of service in 5G core networks.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"smf","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 SMF provides Session Management Function for free5GC, an open-source project for 5th generation (5G) mobile core networks. In versions up to and including 1.4.1, SMF panics and terminates when processing a malformed PFCP SessionReportRequest on the PFCP (UDP/8805) interface. No known upstream fix is available, but some workarounds are available. ACL/firewall the PFCP interface so only trusted UPF IPs can reach SMF (reduce spoofing/abuse surface); drop/inspect malformed PFCP SessionReportRequest messages at the network edge where feasible, and/or add recover() around PFCP handler dispatch to avoid whole-process termination (mitigation only).","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":"Null dereference in smf","id":"CVE-2026-26025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"GLPI has a Server-Side Template Injection via Double-Compilation","id":"CVE-2026-26026"},"packages":[],"prev":{"headline":"Null dereference in smf","id":"CVE-2026-26024"},"products":["smf"],"published":"2026-02-24","related":[{"cvss_score":6.6,"headline":"Null dereference in smf","id":"CVE-2026-25501","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":6.6,"headline":"Null dereference in smf","id":"CVE-2026-26024","kev_date_added":null,"published":"2026-02-24"}],"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":"Attackers can crash the free5GC SMF by sending malformed PFCP messages, causing denial of service in 5G core networks.","url":"https://insights.sbomify.com/CVE-2026-26025/"}