FortideceptorApplication · Fortinet
CVE-2026-25690
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 improper neutralization of argument delimiters in a command ('argument injection') vulnerability in Fortinet FortiDeceptor 6.0.0 through 6.0.2, FortiDeceptor 5.3.0 through 5.3.3, FortiDeceptor 5.2.0 through 5.2.1, FortiDeceptor 5.1 all versions, FortiDeceptor 5.0 all versions may allow an authenticated attacker with at least read-only admin permission to read log files via HTTP 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 · high confidenceFortiDeceptor contains an argument injection vulnerability where improper neutralization of argument delimiters in a command allows an authenticated attacker with at least read-only admin permissions to read arbitrary log files via crafted HTTP requests. The attacker exploits the lack of input sanitization to inject arguments that cause the application to access unintended log files.
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
FortideceptorApplication
>= 5.0.0, <= 5.1.0>= 5.3.0, <= 5.3.3>= 6.0.0, <= 6.0.2= 5.2.0= 5.2.1CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 FortiDeceptor installed versionLog into the FortiDeceptor CLI and run: 'get system status' or access the web UI Dashboard to view the firmware version displayed under System InformationAffected if The displayed version falls within 5.0.0-5.1.0, 5.2.0-5.2.1, 5.3.0-5.3.3, or 6.0.0-6.0.2
-
Confirm administrative access is enabledIn the web UI, go to System > Administrators or run 'get system admin' in CLI to list admin accounts. Verify if any accounts with read-only or higher privileges existAffected if Any authenticated admin account (read-only or higher) exists, allowing the argument injection to be exploited
-
Verify HTTP management interface exposureCheck network configuration by running 'get system interface' in CLI or reviewing network settings in the web UI to determine if the management interface is accessible via HTTPAffected if The management interface is reachable over HTTP (not just HTTPS), increasing exposure to remote exploitation
-
Inspect log file accessibilityAccess the web UI and navigate to Log & Report > Log Settings or run 'diagnose log test' to confirm log files are present and the system can read arbitrary log files via crafted requestsAffected if Log files are stored on the system and accessible through the web interface, which the argument injection could exploit
A user is affected if their FortiDeceptor version is within the affected ranges (5.0.0-5.1.0, 5.2.0-5.2.1, 5.3.0-5.3.3, or 6.0.0-6.0.2) AND the management interface is accessible to authenticated administrators who could exploit the argument injection to read arbitrary log files.
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.
From vendor dataUpgrade FortiDeceptor to the latest patched version per Fortinet's security advisory. If immediate patching is not possible, restrict administrative access to trusted personnel only and monitor HTTP requests for anomalous patterns.
Fix this in Fortideceptor
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25690 — 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-2026-25690 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