Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-25815: CWE-1394 Use of Default Cryptographic Key in Fortinet FortiOS

0
Low
VulnerabilityCVE-2026-25815cvecve-2026-25815cwe-1394
Published: Thu Feb 05 2026 (02/05/2026, 21:14:09 UTC)
Source: CVE Database V5
Vendor/Project: Fortinet
Product: FortiOS

Description

CVE-2026-25815 is a vulnerability in Fortinet FortiOS up to version 7. 6. 6 where LDAP credentials stored in device configuration files can be decrypted by attackers due to the use of a default cryptographic key shared across all installations. The vendor considers this a non-vulnerability if customers enable a non-default encryption option, but this option is disabled by default because it can disrupt functionality. The vulnerability has a low CVSS score (3. 2) with limited attack vector and impact, requiring local access and high attack complexity. No known exploits are reported in the wild. European organizations using FortiOS devices with default settings risk exposure of LDAP credentials, potentially leading to credential compromise. Mitigation involves enabling the stronger encryption option despite potential operational impacts and restricting access to configuration files. Countries with high Fortinet market penetration and critical infrastructure using FortiOS are more likely to be affected.

AI-Powered Analysis

AILast updated: 02/05/2026, 21:44:36 UTC

Technical Analysis

CVE-2026-25815 identifies a cryptographic weakness in Fortinet FortiOS versions through 7.6.6, where LDAP credentials stored within device configuration files are encrypted using a default cryptographic key that is identical across all customer installations. This design flaw corresponds to CWE-1394, 'Use of Default Cryptographic Key,' which undermines the confidentiality of sensitive credentials. Attackers with local access to the device configuration files can decrypt these LDAP credentials without needing authentication or user interaction. The vulnerability arises because Fortinet’s default configuration does not enable a stronger encryption option that uses unique keys per installation; this option is disabled by default due to potential disruptions in device management functionality, as documented in Fortinet’s 'Managing FortiGates with private data encryption' guide. The CVSS v3.1 base score is 3.2 (low severity), reflecting a local attack vector, high attack complexity, no privileges required, no user interaction, and limited confidentiality impact. No known exploits have been observed in the wild as of the publication date. The vulnerability affects all FortiOS devices up to version 7.6.6 that have not enabled the recommended encryption setting. This weakness could allow attackers who gain access to configuration files—through other means such as compromised administrative credentials or physical access—to extract LDAP credentials, potentially facilitating further lateral movement or privilege escalation within enterprise networks.

Potential Impact

For European organizations, the exposure of LDAP credentials due to this vulnerability can lead to unauthorized access to directory services, which are critical for authentication and authorization across enterprise environments. Compromise of LDAP credentials may enable attackers to impersonate users, escalate privileges, or access sensitive resources, undermining confidentiality and potentially integrity of systems. Although the vulnerability requires local access to configuration files, attackers who have already breached perimeter defenses or insider threats could exploit this to deepen their foothold. The low CVSS score reflects limited direct impact and high exploitation complexity, but the cascading effects of credential compromise in complex enterprise networks can be significant. Organizations relying heavily on Fortinet FortiOS for network security and authentication infrastructure, especially those in regulated sectors such as finance, healthcare, and critical infrastructure within Europe, face increased risk. The default use of a shared cryptographic key across all installations amplifies the risk since compromise of one device’s configuration could reveal credentials applicable to others if reused. However, the lack of known active exploitation reduces immediate threat urgency.

Mitigation Recommendations

European organizations should prioritize enabling the non-default private data encryption option in FortiOS that uses unique cryptographic keys per installation, despite potential operational disruptions. This setting is documented by Fortinet and is the definitive fix to eliminate the use of default cryptographic keys. Before enabling, thorough testing in controlled environments is recommended to assess and mitigate any functional impacts on device management workflows. Additionally, organizations should enforce strict access controls to FortiOS configuration files, limiting access to trusted administrators and using secure storage and transmission methods. Regular audits and monitoring for unauthorized access to configuration files can help detect potential exploitation attempts. Network segmentation and strong endpoint security can reduce the risk of attackers gaining local access to devices. Organizations should also keep FortiOS firmware updated and monitor Fortinet advisories for patches or improvements addressing this issue. Finally, consider integrating multi-factor authentication and enhanced logging around LDAP and FortiOS administrative access to detect anomalous activities early.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-02-05T21:14:09.087Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69850be1f9fa50a62f3fbedd

Added to database: 2/5/2026, 9:30:09 PM

Last enriched: 2/5/2026, 9:44:36 PM

Last updated: 2/5/2026, 11:08:10 PM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats