CVE
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.0.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. 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. The FGFM configuration-sync mesh is reached using the default pre-shared key.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach14/20Affects Fortinet (an enterprise product or network appliance)
- Severity8/10CVSS 8.0
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
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. The FGFM configuration-sync mesh is reached using the default pre-shared key.Upgrade to a fixed version: 8.0.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126181
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: cve.now feed data
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: fortiguard.fortinet.com, cve.org
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: cve.now feed data
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: fortiguard.fortinet.com, cve.org
How do I fix CVE-2026-126181?
Upgrade to FortiManager 8.0.2 or above, as the advisory directs.Source: fortiguard.fortinet.com, cve.org