{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-126178 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-126178 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-126178 is a high-severity memory corruption vulnerability in Fortinet FortiAnalyzer, published on 11 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-126178 and fix it if it is affected.\n\nWhat it is: CVE-2026-126178 is a high-severity memory corruption vulnerability in Fortinet FortiAnalyzer, published on 11 Nov 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-126178 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\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-2026-126178/ (Markdown: https://insights.sbomify.com/CVE-2026-126178/index.md)","id":"CVE-2026-126178","markdown":"https://insights.sbomify.com/CVE-2026-126178/index.md","name":"CVE-2026-126178","record":{"aliases":["GHSA-55q4-rggf-jgw6"],"analysis":{"component_type":"network_device","exploitable_when_present":false,"fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"network management appliance","requires_auth":"high_privilege","requires_specific_call":false,"summary":"An authenticated admin can trigger a heap overflow via a crafted request to execute code on FortiAnalyzer and FortiManager; Fortinet customers should care.","user_interaction":"not_required","vuln_class":"memory_corruption","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"fortinet","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"A heap-based buffer overflow vulnerability in Fortinet FortiAnalyzer 8.0.0 through 8.0.1, FortiAnalyzer 7.6.0 through 7.6.7, FortiAnalyzer 7.4.0 through 7.4.11, FortiAnalyzer 7.2.0 through 7.2.12, FortiAnalyzer Cloud 8.0.0 through 8.0.1, FortiAnalyzer Cloud 7.6.0 through 7.6.7, FortiAnalyzer Cloud 7.4.1 through 7.4.11, FortiAnalyzer Cloud 7.2.1 through 7.2.12, FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager 7.4.0 through 7.4.11, FortiManager 7.2.0 through 7.2.12, FortiManager Cloud 8.0.0 through 8.0.1, FortiManager Cloud 7.6.0 through 7.6.7, FortiManager Cloud 7.4.1 through 7.4.11, FortiManager Cloud 7.2.1 through 7.2.12 may allow an authenticated attacker with admin privileges to execute unauthorized code or commands via a crafted request.","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":"Memory corruption in FortiAnalyzer","id":"CVE-2026-126178","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in FortiAnalyzer","id":"CVE-2026-126179"},"nickname":null,"packages":[],"prev":{"headline":"Other in FortiAnalyzer","id":"CVE-2026-126177"},"products":["FortiAnalyzer","FortiAnalyzer Cloud","FortiManager","FortiManager Cloud"],"published":"2026-11-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-11","vendors":["Fortinet"]},"summary":"An authenticated admin can trigger a heap overflow via a crafted request to execute code on FortiAnalyzer and FortiManager; Fortinet customers should care.","url":"https://insights.sbomify.com/CVE-2026-126178/"}