CVE-2025-53379: A out-of-bounds read vulnerability in Fortinet FortiAuthenticator 6.6.0 through 6.6.2, FortiAuthenticator 6...
A out-of-bounds read vulnerability in Fortinet FortiAuthenticator 6.6.0 through 6.6.2, FortiAuthenticator 6.5 all versions may allow a remote unauthenticated attacker to retrieve sensitive information via a specially crafted request.
Security readout for executives and security teams
Plain-English summary
CVE-2025-53379 is a high-severity Fortinet FortiAuthenticator information disclosure flaw. A remote attacker who is not logged in may be able to retrieve sensitive information by sending a crafted request. The main business concern is exposure of authentication-related data from systems that often sit close to identity and access workflows.
Executive priority
Treat this as a near-term identity infrastructure risk. It is not described as code execution, but unauthenticated sensitive information disclosure on FortiAuthenticator can materially affect security posture. Prioritize exposed systems first and require confirmation against Fortinet guidance.
Technical view
The issue is an out-of-bounds read, CWE-125, in FortiAuthenticator. The CVSS 3.1 score is 7.0 with network access, low complexity, no privileges, no user interaction, and high confidentiality impact. Integrity and availability are not rated as impacted in the supplied source bundle.
Likely exposure
Organizations running FortiAuthenticator versions listed in the bundle, including 6.6.0 through 6.6.2 and listed 6.5, 6.4, and 6.3 builds, should treat reachable instances as potentially exposed. Exposure is higher where FortiAuthenticator interfaces are accessible from untrusted networks.
Exploitation context
The source bundle states remote unauthenticated exploitation may retrieve sensitive information. It does not provide evidence of active exploitation, and KEV is false. No public exploit details are included in the provided sources, so exploitation maturity should not be overstated.
Researcher notes
The evidence supports confidentiality-focused impact only. The source bundle has some affected-version breadth beyond the short description, so researchers should validate exact product branches against Fortinet’s advisory and CVE records. Do not infer active exploitation from severity alone.
Mitigation direction
Review Fortinet PSIRT FG-IR-26-146 for official fixed versions or workarounds.
Inventory all FortiAuthenticator deployments and record exact running versions.
Prioritize remediation for internet-facing or broadly reachable FortiAuthenticator systems.
Restrict access to FortiAuthenticator interfaces to trusted networks where operationally possible.
Monitor Fortinet advisory updates for revised affected-version or remediation details.
Validation and detection
Compare deployed FortiAuthenticator versions against the affected versions in the CVE bundle.
Confirm whether FortiAuthenticator interfaces are reachable without authentication from untrusted networks.
Review access logs for unusual unauthenticated requests to exposed FortiAuthenticator services.
Track whether CISA KEV status changes after this assessment.
Verify remediation status against Fortinet PSIRT guidance, not assumptions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.