Missing AuthenticationWeakness · CWE-306

CVE-2026-8364

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Gladinet Triofox Cloud Server Agent Access Service (GladServerAgentService.exe) listens on TCP port 7878 and processes remote HTTP messages with URL paths starting with /resources, /status, /sysinfo, /woshome, /Settings, /schedule, or /DavCache.

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

Gladinet Triofox Cloud Server Agent (GladServerAgentService.exe) exposes an HTTP service on TCP port 7878 that handles multiple URL endpoints including /resources, /status, /sysinfo, /woshome, /Settings, /schedule, and /DavCache. The critical CVSS score indicates this unauthenticated HTTP interface is likely vulnerable to remote code execution or severe authentication bypass.

MitigationImmediately restrict network access to port 7878 via firewall rules to block external traffic, and contact Gladinet for vendor-supplied patches addressing this critical vulnerability in the Triofox Cloud Server Agent.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify GladServerAgentService.exe is installed and running
    Open Windows Task Manager or run 'tasklist /FI "IMAGENAME eq GladServerAgentService.exe"' in command prompt to see if the service process is active
    Affected if The process GladServerAgentService.exe is running on the system
  2. Confirm TCP port 7878 is listening
    Run 'netstat -an | findstr :7878' or use PowerShell 'Get-NetTCPConnection -LocalPort 7878 -State Listen' to check if the service is bound to port 7878
    Affected if Port 7878 is in LISTENING state and accepting connections
  3. Test unauthenticated HTTP endpoint access
    Use a web browser or curl to request http://localhost:7878/status or http://localhost:7878/sysinfo without providing any credentials
    Affected if The endpoint returns HTTP 200 and exposes system information without authentication
  4. Check network exposure of port 7878
    Run 'netstat -ano | findstr :7878' to identify listening addresses. If listening on 0.0.0.0 or ::, the service is exposed to all network interfaces. Verify with 'Test-NetConnection -ComputerName localhost -Port 7878' from external hosts
    Affected if Port 7878 is bound to 0.0.0.0 or :: and accessible from non-localhost addresses
  5. Compare installed version to available releases
    Right-click GladServerAgentService.exe, select Properties, then Details to view File Version, or query registry under HKLM\Software\Gladinet\Triofox for version keys. Contact vendor or check release notes to determine if current version is older than patched releases
    Affected if Installed version is older than the latest patched version provided by Gladinet

The system is affected if GladServerAgentService.exe is running with port 7878 exposed and accessible without authentication on the network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to port 7878 via firewall rules to block external traffic, and contact Gladinet for vendor-supplied patches addressing this critical vulnerability in the Triofox Cloud Server Agent.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8364 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8364 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