dbcve.org
AgentApplication · Watchguard

CVE-2026-41287

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 1.25.03.0000 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Stack-based Buffer Overflow vulnerability in the WatchGuard Agent discovery service on Windows allows Overflow Buffers. An unauthenticated attacker on the same local network could exploit this vulnerability to crash the agent service.

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 confidence

Stack-based buffer overflow in the WatchGuard Agent discovery service on Windows allows an unauthenticated attacker on the same local network to trigger the vulnerability, causing the agent service to crash.

MitigationApply vendor-supplied patches for WatchGuard Agent when available; meanwhile, restrict network access to the discovery service via firewall rules or network segmentation to limit exposure to local network attackers.

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
AgentApplication
Affected:< 1.25.03.0000

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WatchGuard Agent is installed
    Check for WatchGuard Agent installation via Windows Registry key at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or look for WatchGuard folder in Program Files
    Affected if WatchGuard Agent is present on the system
  2. Determine installed version
    Check the installed version by querying the registry value DisplayVersion under the WatchGuard Agent uninstall key, or right-click the executable and view Properties > Details for File Version
    Affected if Version number is less than 1.25.03.0000
  3. Confirm discovery service is running
    Open Services console (services.msc) and locate the WatchGuard Agent service, or run 'sc query' command to check service status
    Affected if The WatchGuard Agent service is installed and running
  4. Check network exposure to discovery service
    Use 'netstat -an' or 'netsh interface tcp show global' to verify the discovery service port is listening on the network; also check Windows Firewall rules for any inbound rules allowing traffic to WatchGuard ports
    Affected if The discovery service is bound to a network interface and accepting connections from the local network

System is affected if WatchGuard Agent version is below 1.25.03.0000 and the discovery service is running and exposed to the local network

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.25.03.0000 or later
Fixed in 1.25.03.0000
Interim mitigation

Apply vendor-supplied patches for WatchGuard Agent when available; meanwhile, restrict network access to the discovery service via firewall rules or network segmentation to limit exposure to local network attackers.

Recommended fix Moderate confidence

1.25.03.0000 or later

  1. Obtain the WatchGuard Agent version 1.25.03.0000 or later from the official WatchGuard support portal at www.watchguard.com
  2. Ensure all systems running the affected WatchGuard Agent version are backed up before upgrading
  3. Download the appropriate installer for your Windows environment from WatchGuard's software distribution
  4. Stop the WatchGuard Agent service on the target Windows system
  5. Run the installer to upgrade the WatchGuard Agent to version 1.25.03.0000 or newer
  6. Restart the Windows system or restart the WatchGuard Agent service to ensure the update is fully applied
  7. Verify the installed version by checking the Agent properties to confirm the upgrade was successful
  8. Repeat the upgrade process on all affected systems on the local network

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agent Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41287 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41287 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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