Skip to content

NetworksHigh 8.0

CVE-2026-126181

Hard-coded PSK allows adjacent attacker to join FortiGate FGFM config-sync mesh.

How scary is it?

updated 22 Nov 2026
  • No

    Works without logging in1

    Needs a login: a basic user account (CVSS PR:L).

  • No

    Reachable over the network1

    Needs access to the same local network (CVSS AV:A).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild

    None reported that we know of.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run Fortinet FortiManager in an affected version>= 8.0.0 and <= 8.0.1 / >= 7.6.0 and <= 7.6.7 / >= 7.4.0 and <= 7.4.11 (+1 more)

    >= 8.0.0 and <= 8.0.1 >= 7.6.0 and <= 7.6.7 >= 7.4.0 and <= 7.4.11 >= 7.2.0 and <= 7.2.13

    The CVE record states no fixed release.

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker is on the same local network

    CVSS attack vector: Adjacent (AV:A). Same subnet or link layer.

    Source 1

  3. The attacker has a user account

    CVSS privileges required: Low (PR:L). The attacker needs basic user privileges.

    Source 1

  4. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Recommendation, AI-writtenFollow Fortinet advisory; apply vendor fixes or isolate FortiManager and rotate PSKs.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. FortiManager is widely used for managing FortiGate fleets; a hard-coded PSK allowing mesh join can enable config injection or disruption across network infrastructure.

CVSS
8.0Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
0.13%chance of exploitation in the next 30 daystop 98% of scored CVEsFIRST score of 21 Nov 2026
Fix
Not stated by the vendorno fixed release in the CVE record
Published
11 Nov 2026analysed here 14 Nov 2026

Summary

Impact

Attacker can join FGFM mesh using default PSK to inject or alter configurations, enable lateral movement, or disrupt device sync.

Triage

Attack surface
Server-side
Exploitable
Configuration or build time
Attack vector
adjacent network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Fortinet FortiManager>= 8.0.0 and <= 8.0.1>= 7.6.0 and <= 7.6.7>= 7.4.0 and <= 7.4.11>= 7.2.0 and <= 7.2.13Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • FortiManager 8.0.0 - 8.0.1
  • FortiManager 7.6.0 - 7.6.7
  • FortiManager 7.4.0 - 7.4.11
  • FortiManager 7.2 (all versions)
  • FortiGate FGFM deployments managed by affected FortiManager

Fix and mitigation

Action required

Patch when possible

WAF and other mitigations

Can a WAF block it? No. The vulnerability involves a hard-coded pre-shared key allowing an adjacent attacker to join a configuration synchronization mesh, which is a network-level protocol, not HTTP-based. Therefore, a web application firewall cannot filter or block the attack.

Also consider: patch · rotate

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

Timeline

  1. 11 Nov 2026Published
  2. 11 Nov 2026CVE record last updatedsame day later
  3. 14 Nov 2026Analysed by vulneraibility.com3 days later

Common questions

Is CVE-2026-126181 being exploited?

Not confirmed. CVE-2026-126181 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-126181?

CVE-2026-126181 is rated High with a CVSS score of 8.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-126181?

Not known from our data. No patch reference has been recorded for CVE-2026-126181, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-126181 affect?

CVE-2026-126181 affects FortiManager 8.0.0 - 8.0.1, FortiManager 7.6.0 - 7.6.7, FortiManager 7.4.0 - 7.4.11, FortiManager 7.2 (all versions), and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-126181?

Follow Fortinet advisory; apply vendor fixes or isolate FortiManager and rotate PSKs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Other links (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.