{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1974 exists.","fix":"No fix has been published for CVE-2026-1974 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-1974 is a medium-severity denial of service vulnerability in Free5gc Free5gc, published on 6 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-1974 and fix it if it is affected.\n\nWhat it is: CVE-2026-1974 is a medium-severity denial of service vulnerability in Free5gc Free5gc, published on 6 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-2026-1974 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-2026-1974/ (Markdown: https://insights.sbomify.com/CVE-2026-1974/index.md)","id":"CVE-2026-1974","markdown":"https://insights.sbomify.com/CVE-2026-1974/index.md","name":"CVE-2026-1974","record":{"aliases":["GHSA-jr33-9q9c-ppp3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"5G Core Network","requires_auth":"none","summary":"Remote attackers can cause a denial of service in Free5GC SMF via the ResolveNodeIdToIp function, requiring a patch to mitigate.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"free5gc","vendor":"free5gc"}],"cvss":{"score":6.9,"severity":"medium","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:P","version":"4.0"},"cwes":[{"id":"CWE-404","name":"Improper Resource Shutdown or Release"}],"description":"A vulnerability was identified in Free5GC up to 4.1.0. This affects the function ResolveNodeIdToIp of the file internal/sbi/processor/datapath.go of the component SMF. The manipulation leads to denial of service. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. It is recommended to apply a patch to fix this issue.","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":"Free5GC SMF datapath.go ResolveNodeIdToIp denial of service","id":"CVE-2026-1974","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"free5gc:free5gc","products":["free5gc:free5gc"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"Free5GC pfcp_reports.go identityTriggerType null pointer dereference","id":"CVE-2026-1975"},"packages":[],"prev":{"headline":"Free5GC SMF establishPfcpSession null pointer dereference","id":"CVE-2026-1973"},"products":["Free5GC"],"published":"2026-02-06","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-23","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service in Free5GC SMF via the ResolveNodeIdToIp function, requiring a patch to mitigate.","url":"https://insights.sbomify.com/CVE-2026-1974/"}