{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70123 exists.","fix":"No fix has been published for CVE-2025-70123 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70123 is a high-severity denial of service vulnerability in Free5gc Free5gc, published on 13 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-70123 and fix it if it is affected.\n\nWhat it is: CVE-2025-70123 is a high-severity denial of service vulnerability in Free5gc Free5gc, published on 13 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70123 exists.\n\nAffected product: Free5gc Free5gc. 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-70123/ (Markdown: https://insights.sbomify.com/CVE-2025-70123/index.md)","id":"CVE-2025-70123","markdown":"https://insights.sbomify.com/CVE-2025-70123/index.md","name":"CVE-2025-70123","record":{"aliases":["GHSA-j98c-62jj-x3h3"],"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","requires_auth":"none","summary":"Remote attackers can cause denial of service in free5GC UPF by sending malformed PFCP requests, disrupting SMF connections and service availability.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"free5gc","vendor":"free5gc"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An improper input validation and protocol compliance vulnerability in free5GC v4.0.1 allows remote attackers to cause a denial of service. The UPF incorrectly accepts a malformed PFCP Association Setup Request, violating 3GPP TS 29.244. This places the UPF in an inconsistent state where a subsequent valid PFCP Session Establishment Request triggers a cascading failure, disrupting the SMF connection and causing service degradation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Denial of service in n/a","id":"CVE-2025-70123","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"free5gc:free5gc","products":["free5gc:free5gc"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-70128"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-70122"},"products":["n/a"],"published":"2026-02-13","related":[{"cvss_score":10,"headline":"free5GC: NEF nnef-oam route group is unauthenticated; no-token requests reach the OAM handler","id":"CVE-2026-44327","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":10,"headline":"free5GC's SMF UPI management interface lacks auth middleware; unauthenticated topology read/write requests reach handlers","id":"CVE-2026-44329","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":10,"headline":"free5GC's NEF nnef-pfdmanagement API is unauthenticated; forged bearer tokens can read PFD data and create/delete PFD subscriptions","id":"CVE-2026-44330","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-63679","kev_date_added":null,"published":"2025-11-12"},{"cvss_score":9.4,"headline":"free5GC's NEF 3gpp-pfd-management API is unauthenticated; forged bearer tokens can create, read, and delete PFD transactions","id":"CVE-2026-44315","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":9.4,"headline":"free5GC's NEF 3gpp-traffic-influence API is unauthenticated; missing or forged bearer tokens can create, read, patch, and delete subscriptions","id":"CVE-2026-44326","kev_date_added":null,"published":"2026-05-27"},{"cvss_score":8.7,"headline":"free5gc UDR improper path validation allows unauthenticated access to Traffic Influence Subscriptions","id":"CVE-2026-40247","kev_date_added":null,"published":"2026-04-16"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-13","vendors":["n/a"]},"summary":"Remote attackers can cause denial of service in free5GC UPF by sending malformed PFCP requests, disrupting SMF connections and service availability.","url":"https://insights.sbomify.com/CVE-2025-70123/"}