{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-61099 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-61099 is a high-severity vulnerability in n/a, published on 27 Oct 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-61099 and fix it if it is affected.\n\nWhat it is: CVE-2025-61099 is a high-severity vulnerability in n/a, published on 27 Oct 2025. 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-61099 in the wild and no public exploit code.\n\nAffected product: n/a. 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-61099/ (Markdown: https://insights.sbomify.com/CVE-2025-61099/index.md)","id":"CVE-2025-61099","markdown":"https://insights.sbomify.com/CVE-2025-61099/index.md","name":"CVE-2025-61099","record":{"aliases":["AZL-69619","AZL-69622","DEBIAN-CVE-2025-61099","GHSA-6xr9-vq37-4x64","UBUNTU-CVE-2025-61099"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"FRRouting network stack","requires_auth":"none","summary":"Attackers can cause a Denial of Service in FRRouting by sending a crafted LS Update packet that triggers a NULL pointer dereference.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"frrouting","vendor":"frrouting"}],"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-476","name":"NULL Pointer Dereference"}],"description":"FRRouting/frr from v2.0 through v10.4.1 was discovered to contain a NULL pointer dereference via the opaque_info_detail function at ospf_opaque.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted LS Update packet.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Null dereference in n/a","id":"CVE-2025-61099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Null dereference in n/a","id":"CVE-2025-61100"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-61096"},"products":["n/a"],"published":"2025-10-27","related":[{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2024-44070","kev_date_added":null,"published":"2024-08-19"},{"cvss_score":9.8,"headline":"bgpd/bgp_flowspec.c in FRRouting (FRR) before 8.4.3 mishandles an nlri length of zero, aka a \"flowspec overflow.\"","id":"CVE-2023-38406","kev_date_added":null,"published":"2023-11-06"},{"cvss_score":8.1,"headline":"Use after free in n/a","id":"CVE-2022-37035","kev_date_added":null,"published":"2022-08-02"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26127","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26128","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.8,"headline":"Memory corruption in FRRouting","id":"CVE-2022-26129","kev_date_added":null,"published":"2022-03-03"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2026-37457","kev_date_added":null,"published":"2026-05-01"}],"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":"2025-10-28","vendors":["n/a"]},"summary":"Attackers can cause a Denial of Service in FRRouting by sending a crafted LS Update packet that triggers a NULL pointer dereference.","url":"https://insights.sbomify.com/CVE-2025-61099/"}