{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-6787 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-6787 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-6787 is a high-severity vulnerability in WatchGuard Agent, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-6787 and fix it if it is affected.\n\nWhat it is: CVE-2026-6787 is a high-severity vulnerability in WatchGuard Agent, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-6787 in the wild and no public exploit code.\n\nAffected product: WatchGuard Agent. 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-6787/ (Markdown: https://insights.sbomify.com/CVE-2026-6787/index.md)","id":"CVE-2026-6787","markdown":"https://insights.sbomify.com/CVE-2026-6787/index.md","name":"CVE-2026-6787","record":{"aliases":["GHSA-m376-6rq6-f84p"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WatchGuard Agent","requires_auth":"low_privilege","summary":"Hard-coded cryptographic keys in WatchGuard Agent allow attackers to inject code into existing processes on Windows systems.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WatchGuard","cpe":[{"product":"agent","vendor":"watchguard"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"Use of Hard-coded Cryptographic Key vulnerability in WatchGuard Agent on Windows allows Inclusion of Code in Existing Process.","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":"Usage of a hard-coded cryptographic key in WatchGuard Agent allows inclusion of code into existing process","id":"CVE-2026-6787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Uncontrolled search path in PluginLauncher allows SYSTEM code execution in WatchGuard Agent","id":"CVE-2026-6788"},"packages":[],"prev":{"headline":"Memory safety bugs fixed in Firefox ESR 140.10, Thunderbird ESR 140.10, Firefox 150 and Thunderbird 150","id":"CVE-2026-6786"},"products":["WatchGuard Agent"],"published":"2026-05-06","related":[{"cvss_score":8.5,"headline":"Uncontrolled search path in PluginLauncher allows SYSTEM code execution in WatchGuard Agent","id":"CVE-2026-6788","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.3,"headline":"WatchGuard Agent on Windows Privilege Escalation Vulnerability","id":"CVE-2026-41288","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.1,"headline":"Stack-based Buffer Overflow in WatchGuard Agent Discovery Service on Windows Causes Denial of Service - Variant B","id":"CVE-2026-41286","kev_date_added":null,"published":"2026-05-06"},{"cvss_score":7.1,"headline":"Stack-based Buffer Overflow in WatchGuard Agent Discovery Service on Windows Causes Denial of Service - Variant A","id":"CVE-2026-41287","kev_date_added":null,"published":"2026-05-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":"total"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["WatchGuard"]},"summary":"Hard-coded cryptographic keys in WatchGuard Agent allow attackers to inject code into existing processes on Windows systems.","url":"https://insights.sbomify.com/CVE-2026-6787/"}