{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-65562 exists.","fix":"No fix has been published for CVE-2025-65562 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65562 is a high-severity vulnerability in Free5gc Free5gc, published on 18 Dec 2025. 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-65562 and fix it if it is affected.\n\nWhat it is: CVE-2025-65562 is a high-severity vulnerability in Free5gc Free5gc, published on 18 Dec 2025. 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-65562 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-65562/ (Markdown: https://insights.sbomify.com/CVE-2025-65562/index.md)","id":"CVE-2025-65562","markdown":"https://insights.sbomify.com/CVE-2025-65562/index.md","name":"CVE-2025-65562","record":{"aliases":["GHSA-7jcm-x89q-2vg2"],"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 Function","requires_auth":"none","summary":"An unauthenticated remote attacker can crash the free5GC UPF by sending a PFCP request with a large SEID, causing an integer underflow and panic.","user_interaction":"not_required","vuln_class":"integer_overflow"},"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-129","name":"Improper Validation of Array Index"}],"description":"The free5GC UPF suffers from a lack of bounds checking on the SEID when processing PFCP Session Deletion Requests. An unauthenticated remote attacker can send a request with a very large SEID (e.g., 0xFFFFFFFFFFFFFFFF) that causes an integer conversion/underflow in LocalNode.DeleteSess() / LocalNode.Sess() when a uint64 SEID is converted to int and used in index arithmetic. This leads to a negative index into n.sess and a Go runtime panic, resulting in a denial of service (UPF crash). The issue has been reproduced on free5GC v4.1.0 with crashes observed in the session lookup/deletion path in internal/pfcp/node.go; other versions may also be affected. No authentication is required.","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":"Integer overflow in n/a","id":"CVE-2025-65562","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"free5gc:free5gc","products":["free5gc:free5gc"],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-65563"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-65561"},"products":["n/a"],"published":"2025-12-18","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":"2025-12-19","vendors":["n/a"]},"summary":"An unauthenticated remote attacker can crash the free5GC UPF by sending a PFCP request with a large SEID, causing an integer underflow and panic.","url":"https://insights.sbomify.com/CVE-2025-65562/"}