cve.bz

CVE-2026-126160 fortinet fortimail: Improper Authentication

8.2 highEPSS 0.5%

High (8.2) in fortinet fortimail. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
A improper authentication vulnerability in Fortinet FortiMail 8.0.0 through 8.0.1, FortiMail 7.6.0 through 7.6.6, FortiMail 7.4.0 through 7.4.8, FortiMail 7.2 all versions may allow an unauthenticated attacker to escalate privileges and release or delete quarantined messages for arbitrary mailboxes via a crafted quarantine release requests.

Severity

CVSS 3.1

8.2 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
0.5% estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
fortinet (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

ChatGPTClaudeGoogle AI Mode

Show the promptExplain CVE-2026-126160 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126160?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126160?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126160 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126160

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126160](https://cve.bz/cve/badge/CVE-2026-126160.svg)](https://cve.bz/cve/CVE-2026-126160)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126160"><img src="https://cve.bz/cve/badge/CVE-2026-126160.svg" alt="CVE-2026-126160"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Fortinet FortiMailfrom 8.0.0 through 8.0.1
Fortinet FortiMailfrom 7.6.0 through 7.6.6
Fortinet FortiMailfrom 7.4.0 through 7.4.8
Fortinet FortiMailfrom 7.2.0 through 7.2.9

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON