CVE-2025-57740
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn Heap-based Buffer Overflow vulnerability [CWE-122] in FortiOS version 7.6.2 and below, version 7.4.7 and below, version 7.2.10 and below, 7.0 all versions, 6.4 all versions; FortiPAM version 1.5.0, version 1.4.2 and below, 1.3 all versions, 1.2 all versions, 1.1 all versions, 1.0 all versions and FortiProxy version 7.6.2 and below, version 7.4.3 and below, 7.2 all versions, 7.0 all versions RDP bookmark connection may allow an authenticated user to execute unauthorized code via crafted requests.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA heap-based buffer overflow vulnerability (CWE-122) exists in the RDP bookmark connection functionality of FortiOS, FortiPAM, and FortiProxy. An authenticated user can exploit this vulnerability through crafted requests to execute unauthorized code remotely, potentially gaining full control of the affected device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.0.0, < 7.4.4>= 7.6.0, < 7.6.3>= 1.0.0, < 1.4.3= 1.5.0>= 6.4.0, < 7.2.11>= 7.4.0, < 7.4.8>= 7.6.0, < 7.6.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify product and installed versionAccess the Fortinet device CLI or GUI and run the command: 'get system status' (CLI) or check System > Settings > Firmware (GUI). Note the exact version number displayed.Affected if The product is FortiOS, FortiPAM, or FortiProxy and the version falls within these ranges: FortiOS >= 6.4.0 and < 7.2.11, or >= 7.4.0 and < 7.4.8, or >= 7.6.0 and < 7.6.3; FortiPAM >= 1.0.0 and < 1.4.3, or = 1.5.0; FortiProxy >= 7.0.0 and < 7.4.4, or >= 7.6.0 and < 7.6.3
-
Verify RDP bookmark feature is in useIn FortiOS/FortiProxy GUI, navigate to Policy & Objects > Proxy Settings > RDP Bookmarks (or 'execute vpn ssl web url-bookmark list' in CLI). In FortiPAM, check Remote Access > RDP Connections. Review whether any RDP bookmark entries are configured.Affected if RDP bookmarks are created, configured, or have been used in the proxy policy.
-
Confirm administrator access existsCheck user accounts with privileged access via 'show system admin' (CLI) or System > Administrators (GUI). Verify if accounts with sufficient privileges to create or modify RDP bookmarks exist.Affected if Authenticated administrators with permission to configure RDP bookmarks exist in the system.
The environment is affected if the installed FortiOS, FortiPAM, or FortiProxy version is within the affected ranges AND RDP bookmark functionality is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.4.37.2.117.4.4
Upgrade FortiOS to version 7.4.8+, 7.2.11+, 7.6.3+ (or 7.0+/6.4+ to a supported version), FortiPAM to 1.4.3+/1.5.1+, and FortiProxy to 7.4.4+, 7.6.3+ (or 7.0-7.2 to a supported version). Apply principle of least privilege to RDP bookmark permissions and restrict network access to management interfaces.
FortiOS: 7.2.11+, 7.4.8+, or 7.6.3+ | FortiPAM: 1.4.3+ | FortiProxy: 7.4.4+ or 7.6.3+
- 1. Identify the Fortinet product in use (FortiOS, FortiPAM, or FortiProxy) and current version via the web UI or CLI: `get system status`
- 2. For FortiOS: Upgrade to version 7.2.11 or later, 7.4.8 or later, or 7.6.3 or later depending on your branch
- 3. For FortiPAM: Upgrade to version 1.4.3 or later (version 1.5.0 is also affected)
- 4. For FortiProxy: Upgrade to version 7.4.4 or later or 7.6.3 or later depending on your branch
- 5. Download the appropriate firmware from Fortinet's support portal (fortinet.com/support)
- 6. Upload and install the firmware via the FortiOS/FortiPAM/FortiProxy web UI or CLI: `execute upgrade`
- 7. After upgrade, verify the new version is installed and the RDP bookmark functionality works as expected
- 8. Validate that the vulnerability is resolved by confirming the version is at or above the fixed release for your branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57740 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-57740 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data