Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-84390. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-84390 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-84390. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-84390 using CVSS 9.8, EPSS 1%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

criticalInfo Disclosure

CVE-2026-84390

CVE-2026-84390 — A inclusion of sensitive information in source code vulnerability in Fortinet FortiMonitorOnSight 7.2.4 through 7.2.7, FortiMonitorOnSight…

Q: What is CVE-2026-84390?

CVE-2026-84390 is A inclusion of sensitive information in source code vulnerability in Fortinet FortiMonitorOnSight 7.2.4 through 7.2.7, FortiMonitorOnSight…. The supplied enrichment data classifies it as Info Disclosure mapped to CWE-540 CWE-540.

A inclusion of sensitive information in source code vulnerability in Fortinet FortiMonitorOnSight 7.2.4 through 7.2.7, FortiMonitorOnSight 7.2.0 through 7.2.2 may allow attacker to improper access control via <insert attack vector here>

Published Sep 11, 2026Updated Sep 11, 2026Sources: NVD, Fortinet (CNA), GitHub

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

Fortinet

2 products listed

CVSS base

9.8

critical · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade to FortiMonitorOnSight version 7.2.8 or above

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Fortinet	FortiMonitorOnSight	7.2.4 to <= 7.2.7	Vulnerable
Fortinet	FortiMonitorOnSight	7.2.0 to <= 7.2.2	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
9.8	CVSS 3.1	critical	3.9	5.9	Fortinet (CNA)
9.6	CVSS 3.1	critical	—	—	Fortinet (CNA)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weakness & attack patterns

CWE-540

Inferred from the weakness class — not observed against this CVE.

CAPEC-116 · ExcavationCAPEC-118 · Collect and Analyze Information

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable FortiMonitorOnSight.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 9.8 (AV:N)
Sep 11, 2026 · NVD
Initial · CVE published
Sep 11, 2026 · NVD

References

1 on the record

fortiguard.fortinet.com/psirt/FG-IR-26-170
Vendor Advisory

Elsewhere on this site

Fortinetevery CVE for this vendor
Info Disclosuresame class
CWE-540other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-84390 is A inclusion of sensitive information in source code vulnerability in Fortinet FortiMonitorOnSight 7.2.4 through 7.2.7, FortiMonitorOnSight…, a critical vulnerability affecting FortiMonitorOnSight from Fortinet. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-84390. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-84390. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.8 describes technical severity, while EPSS 1% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.