# CVE-2026-78498: Dimension Server-Side Request Forgery via Email Server Test Settings

> An authenticated privileged attacker can exploit an SSRF vulnerability in WatchGuard Dimension to enumerate network services on adjacent systems.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-27h4-xhmx-rq4q

## What is CVE-2026-78498?

CVE-2026-78498 is a medium-severity server-side request forgery vulnerability in WatchGuard Dimension, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A server-side request forgery (SSRF) vulnerability WatchGuard Dimension Email Server Test configuration allows an authenticated privileged attacker to enumerate exposed network services on adjacent network systems.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-78498?


## How do I fix CVE-2026-78498?

No fix has been published for CVE-2026-78498 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-78498 being exploited?

There is no known exploitation of CVE-2026-78498 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-78498 and fix it if it is affected.

What it is: CVE-2026-78498 is a medium-severity server-side request forgery vulnerability in WatchGuard Dimension, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78498 in the wild and no public exploit code.

Affected product: WatchGuard Dimension. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-78498/ (Markdown: https://insights.sbomify.com/CVE-2026-78498/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-78498
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-78498
- OSV: https://osv.dev/vulnerability/CVE-2026-78498

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-78498/
Summaries are generated and may contain mistakes; the official description above is the record.