Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-84390 – Authentication Bypass via Hardcoded JWT Secret – FortiMonitorOnSight 7.2.0–7.2.7

Be the first to know when new zero-days emerge:

Summary

CVE-2026-84390 is a critical vulnerability (CWE-540: Inclusion of Sensitive Information in Source Code) affecting the FortiMonitorOnSight web portal. A hardcoded/exposed secret embedded in the application’s source code allows a remote, unauthenticated attacker to forge or reuse a valid JSON Web Token (JWT) and bypass authentication entirely, gaining administrative-level access to the portal. The issue carries a CVSS v3.1 base score of 9.6 (Critical).

Technical details

  • Root cause: Sensitive information (a JWT signing/verification secret) is embedded directly in FortiMonitorOnSight’s source code (CWE-540), rather than being generated or stored securely.
  • Trigger conditions: No authentication, privileges, or user interaction are required — an attacker only needs network access to the exposed FortiMonitorOnSight web portal.
  • Attack vector: Network. An attacker can craft or replay a forged JWT signed with the exposed secret to impersonate legitimate users or administrators.
  • Impact: Full authentication bypass leading to unauthorized administrative access to the FortiMonitorOnSight portal, which centralizes enterprise monitoring data and controls — resulting in high impact to confidentiality, integrity, and availability.

Affected software

  • FortiMonitorOnSight version 7.2.0 through 7.2.2
  • FortiMonitorOnSight version 7.2.4 through 7.2.7

Severity

  • CVSS v3.1 Base Score: 9.6 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade FortiMonitorOnSight to version 7.2.8 or later, where the exposed secret has been remediated.
  • If immediate patching is not possible: Restrict network exposure of the FortiMonitorOnSight web portal to trusted management networks only (e.g., via firewall rules or VPN), and avoid exposing the portal directly to the internet until patched. Monitor authentication logs for anomalous or unexpected administrative sessions.
  • As with any authentication-bypass fix, consider invalidating existing sessions/tokens and rotating any credentials accessible through the portal after upgrading.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge