{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-53845 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-53845 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-53845 is a medium-severity authentication bypass vulnerability in Fortinet Fortianalyzer, published on 14 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-53845 and fix it if it is affected.\n\nWhat it is: CVE-2025-53845 is a medium-severity authentication bypass vulnerability in Fortinet Fortianalyzer, published on 14 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-53845 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-53845/ (Markdown: https://insights.sbomify.com/CVE-2025-53845/index.md)","id":"CVE-2025-53845","markdown":"https://insights.sbomify.com/CVE-2025-53845/index.md","name":"CVE-2025-53845","record":{"aliases":["GHSA-ccxg-x54f-69cx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiAnalyzer","requires_auth":"none","summary":"Unauthenticated attackers can access device health information or cause denial of service via crafted OFTP requests in FortiAnalyzer.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortianalyzer","vendor":"fortinet"}],"cvss":{"score":6.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L/E:P/RL:X/RC:C","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An improper authentication vulnerability [CWE-287] in Fortinet FortiAnalyzer version 7.6.0 through 7.6.3 and before 7.4.6 allows an unauthenticated attacker to obtain information pertaining to the device's health and status, or cause a denial of service via crafted OFTP requests.","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":"Auth bypass in FortiAnalyzer","id":"CVE-2025-53845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortianalyzer","products":["fortinet:fortianalyzer"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in FortiOS","id":"CVE-2025-53847"},"packages":[],"prev":{"headline":"Memory corruption in FortiOS","id":"CVE-2025-53844"},"products":["FortiAnalyzer"],"published":"2025-10-14","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-14","vendors":["Fortinet"]},"summary":"Unauthenticated attackers can access device health information or cause denial of service via crafted OFTP requests in FortiAnalyzer.","url":"https://insights.sbomify.com/CVE-2025-53845/"}