CVE-2025-54971VulnerabilityPublished 18 Nov 2025Updated 14 Jan 2026

CVE-2025-54971: Fortinet FortiADC · Information disclosure

Affects Fortinet FortiADCSource CVE Database V5

Not known to be exploited · CVSS 3.9 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.9Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Temporal metrics

Exploit Code Maturity: Proof-of-Concept
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Proof-of-Concept: Proof-of-concept exploit code is available, or an attack demonstration is not practical for most systems. The code or technique is not functional in all situations and may require substantial modification by a skilled attacker.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Fortinet FortiADC	Affected =7.4.0 =7.2.0 =7.1.0 =7.0.0 =6.2.0	Fixed in–

AI-suggested

1. Restrict read-only admin access strictly to trusted personnel and regularly audit these accounts to ensure no unauthorized users have such privileges. 2. Implement robust logging and monitoring to detect unusual access patterns to FortiADC logs or configuration interfaces. 3. Until patches are available, consider minimizing the logging of sensitive information or configuring log redaction if supported. 4. Use network segmentation and access control lists to limit which users or systems can reach FortiADC management interfaces. 5. Regularly update FortiADC firmware and subscribe to Fortinet security advisories to apply patches promptly once released. 6. Conduct internal security reviews to identify if any exposed passwords have been reused elsewhere and rotate them if necessary. 7. Employ multi-factor authentication for administrative access to reduce the risk of credential compromise. 8. Evaluate alternative methods for storing and handling external resource credentials, such as using secure vaults or encrypted storage, to avoid embedding passwords in logs. 9. Prepare incident response plans that include scenarios involving credential exposure from FortiADC devices.

Description

An exposure of sensitive information to an unauthorized actor vulnerability in Fortinet FortiADC 7.4.0, FortiADC 7.2 all versions, FortiADC 7.1 all versions, FortiADC 7.0 all versions, FortiADC 6.2 all versions may allow an admin with read-only permission to get the external resources password via the logs of the product

Impact

For European organizations, the primary impact is the potential exposure of sensitive credentials used by FortiADC appliances to access external resources such as backend servers, databases, or cloud services. Although the vulnerability requires read-only admin access, which is a privileged level, the unintended disclosure of passwords in logs can enable attackers or insider threats to escalate privileges or move laterally within the network. This could lead to unauthorized access to critical systems, data breaches, or disruption of services. Given FortiADC's role in application delivery and load balancing, compromise could affect availability indirectly by enabling further attacks. The low CVSS score suggests limited immediate risk, but organizations with large Fortinet deployments or those in regulated sectors (finance, healthcare, critical infrastructure) should be cautious. The absence of known exploits reduces urgency but does not eliminate risk, especially if attackers develop techniques to gain read-only admin credentials. European entities relying on FortiADC for secure application delivery must consider this vulnerability in their risk assessments and incident response planning.

References

fortiguard.fortinet.com/psirt/FG-IR-25-686 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jan 2026, 14:48 UTC

Technical details

References

Community reviews

Related threats