CVE-2026-6787
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUse of Hard-coded Cryptographic Key vulnerability in WatchGuard Agent on Windows allows Inclusion of Code in Existing Process.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA hard-coded cryptographic key embedded in WatchGuard Agent for Windows allows an attacker to inject malicious code into the WatchGuard Agent process. An attacker with local access and low privileges could potentially use this hardcoded key to decrypt/encrypt data or authenticate in ways that facilitate code injection into the running agent process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.25.03.0000CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed WatchGuard Agent versionOpen Windows Control Panel, go to Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*WatchGuard*'} | Select-Object Name, VersionAffected if Version is present and less than 1.25.03.0000
-
Verify WatchGuard Agent service statusOpen Services console (services.msc) and locate WatchGuard Agent service, or run: Get-Service -Name *WatchGuard* in PowerShellAffected if Service exists and is running on a version lower than 1.25.03.0000
-
Locate WatchGuard Agent executableCheck common installation paths such as C:\Program Files\WatchGuard\ or C:\Program Files (x86)\WatchGuard\ for the Agent executable (typically wgapi.exe or similar)Affected if Executable exists and file version property shows version below 1.25.03.0000
-
Confirm version via command lineRun: wgapi.exe -v or wgav.exe -v from the installation directory, or use: (Get-Item 'C:\Program Files\WatchGuard\wgapi.exe').VersionInfo.FileVersionAffected if Returned version is less than 1.25.03.0000
Your environment is affected if WatchGuard Agent for Windows is installed and the installed version is any version prior to 1.25.03.0000.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.25.03.0000
Upgrade WatchGuard Agent to version 1.25.03.0000 or later. If immediate patching is not possible, monitor process activity for WatchGuard Agent and restrict local user privileges to minimize attack surface.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6787 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6787 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data