dbcve.org
FortiadcApplication · Fortinet

CVE-2025-48839

MEDIUM · 6.6 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 7.4.8 / 7.6.3 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An Out-of-bounds Write vulnerability [CWE-787] in FortiADC 8.0.0, 7.6.0 through 7.6.2, 7.4.0 through 7.4.7, 7.2 all versions, 7.1 all versions, 7.0 all versions, 6.2 all versions may allow an authenticated attacker to execute arbitrary code via specially crafted HTTP 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 confidence

An out-of-bounds write vulnerability (CWE-787) in FortiADC's HTTP request processing allows authenticated attackers to write beyond allocated memory boundaries via specially crafted HTTP requests, potentially achieving arbitrary code execution.

MitigationApply vendor-supplied patches for FortiADC (upgrade to patched versions as specified by Fortinet) and review administrative access controls to limit the attack surface to trusted personnel only.

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
FortiadcApplication
Affected:>= 6.2.0, < 7.4.8>= 7.6.0, < 7.6.3= 8.0.0

CVSS 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
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check FortiADC firmware version
    Run 'get system status' from CLI or view System > Settings > Dashboard in the web UI to display the firmware version
    Affected if The displayed version falls within >= 6.2.0 and < 7.4.8, OR >= 7.6.0 and < 7.6.3, OR equals 8.0.0
  2. Verify HTTP profiles are configured
    Navigate to Server Load Balance > Virtual Server > Virtual Server in the web UI, or run 'show load-balance virtual-server' in CLI to list configured virtual servers
    Affected if Any virtual server is configured with an HTTP profile (the vulnerability affects HTTP request processing specifically)
  3. Confirm administrative user accounts
    Run 'get system admin user' in CLI or view System > Administrator > Administrators in the web UI to list admin accounts
    Affected if Multiple admin accounts exist or admin accounts with privileged access are present (authentication is required for exploitation)
  4. Review admin access profiles
    Run 'get system accprofile' in CLI or view System > Administrator > Access Profile to examine permission levels assigned to admin accounts
    Affected if Accounts with write or admin-level access profiles exist (authenticated attackers need such access to send malicious HTTP requests)
  5. Check for HTTP virtual server listeners
    Run 'show load-balance virtual-server <name>' for each virtual server to inspect listener settings, looking for port 80 or 443 HTTP/HTTPS listeners
    Affected if HTTP or HTTPS listeners are bound to virtual servers, exposing the HTTP processing path to network traffic

Your FortiADC is affected if the firmware version is within the listed vulnerable ranges AND HTTP virtual servers with listeners are configured and accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.8 / 7.6.3 or later
Fixed in 7.4.87.6.3
Interim mitigation

Apply vendor-supplied patches for FortiADC (upgrade to patched versions as specified by Fortinet) and review administrative access controls to limit the attack surface to trusted personnel only.

Recommended fix High confidence

FortiADC 7.4.8 or later, 7.6.3 or later, or 8.0.1 or later (depending on your current branch)

  1. Identify the currently installed FortiADC version using 'get system status' or 'diagnose sys version' commands
  2. Determine which version branch your current installation belongs to (6.2.x, 7.0.x, 7.1.x, 7.2.x, 7.4.x, 7.6.x, or 8.0.x)
  3. For version 7.4.x: Upgrade to version 7.4.8 or later
  4. For version 7.6.x: Upgrade to version 7.6.3 or later
  5. For version 8.0.x: Upgrade to version 8.0.1 or later when available
  6. For versions 6.2.x, 7.0.x, 7.1.x, 7.2.x: Upgrade to the minimum fixed version in the next available branch (e.g., 7.4.8 or later)
  7. Download the firmware from the Fortinet Customer Support portal after authenticating
  8. Upload the firmware via the web UI (System > Firmware > Upload) or CLI: 'execute restore config' or 'execute upgrade-image'
Caveat Review Fortinet release notes for your target version for any configuration or behavioral changes; test in non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiadc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48839 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48839 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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