{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-67604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-67604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67604 is a medium-severity denial of service vulnerability in Fortinet Fortianalyzer, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-67604 and fix it if it is affected.\n\nWhat it is: CVE-2025-67604 is a medium-severity denial of service vulnerability in Fortinet Fortianalyzer, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-67604 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortianalyzer. 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-67604/ (Markdown: https://insights.sbomify.com/CVE-2025-67604/index.md)","id":"CVE-2025-67604","markdown":"https://insights.sbomify.com/CVE-2025-67604/index.md","name":"CVE-2025-67604","record":{"aliases":["GHSA-c3gv-678x-vgc9"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet log management","requires_auth":"low_privilege","summary":"An authenticated attacker can cause a system hang in FortiAnalyzer and FortiManager by sending multiple specially crafted HTTP requests.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortianalyzer","vendor":"fortinet"},{"product":"fortimanager","vendor":"fortinet"}],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H/E:F/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-676","name":"Use of Potentially Dangerous Function"}],"description":"A use of potentially dangerous function vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.4, FortiAnalyzer 7.4.0 through 7.4.8, FortiAnalyzer 7.2 all versions, FortiAnalyzer 7.0 all versions, FortiAnalyzer 6.4 all versions, FortiManager 7.6.0 through 7.6.4, FortiManager 7.4.0 through 7.4.8, FortiManager 7.2 all versions, FortiManager 7.0 all versions, FortiManager 6.4 all versions may allow an authenticated attacker to cause a system hang via multiple specially crafted HTTP requests causing crashes. This happens if internal locks are aligned, which is out of control of the attacker.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in FortiAnalyzer","id":"CVE-2025-67604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortianalyzer","products":["fortinet:fortianalyzer","fortinet:fortimanager"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Not used","id":"CVE-2025-67605"},"packages":[],"prev":{"headline":"Lack of client authorization allows arbitrary users to influence the firewall configuration","id":"CVE-2025-67603"},"products":["FortiAnalyzer","FortiManager"],"published":"2026-05-12","related":[{"cvss_score":9.4,"headline":"Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-24858","kev_date_added":"2026-01-27","published":"2026-01-27"},{"cvss_score":9.3,"headline":"Memory corruption in FortiAnalyzer","id":"CVE-2023-25610","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":8.8,"headline":"Server-side request forgery in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2021-32603","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":8.8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer","id":"CVE-2020-12817","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":8,"headline":"Auth bypass in FortiOS","id":"CVE-2024-48886","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2022-39950","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":7.8,"headline":"Command injection in Fortinet FortiManager, FortiAnalyzer, FortiPortal","id":"CVE-2021-26104","kev_date_added":null,"published":"2022-04-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["Fortinet"]},"summary":"An authenticated attacker can cause a system hang in FortiAnalyzer and FortiManager by sending multiple specially crafted HTTP requests.","url":"https://insights.sbomify.com/CVE-2025-67604/"}