CVE-2026-8360
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 · uneditedFunction calls to WOSCommonUtil.dll!WOSSysInfoGetDeviceInterface() in various DLLs (i.e., WOSProfileMgrModule.dll, WOSWebDavModule.dll) can return a NULL pointer (i.e., when no user is logged into the Triofox Server Agent Management Console). The returned NULL pointer is not checked before being dereferenced.
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 confidenceA NULL pointer dereference vulnerability exists in Triofox Server Agent where the function WOSSysInfoGetDeviceInterface() in WOSCommonUtil.dll returns NULL when no user is logged into the Triofox Server Agent Management Console. Multiple DLLs (WOSProfileMgrModule.dll, WOSWebDavModule.dll) call this function without checking the return value before dereferencing it, causing a denial of service or potentially arbitrary code execution.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Confirm Triofox Server Agent installationCheck for Triofox Server Agent in installed programs (Windows Add/Remove Programs) or look for installation directory (typically C:\Program Files\Triofox or C:\Program Files (x86)\Triofox)Affected if Triofox Server Agent is installed on the system
-
Identify installed Triofox Server Agent versionCheck the version of Triofox Server Agent in Programs and Features or examine the version property of WOSCommonUtil.dll if found in the installation directoryAffected if The installed version matches the affected product version range (check vendor advisories for specific versions)
-
Locate affected DLL filesSearch for WOSCommonUtil.dll, WOSProfileMgrModule.dll, and WOSWebDavModule.dll in the Triofox installation directory (e.g., server\bin or similar subfolder)Affected if All three DLLs are present in the Triofox installation directory
-
Check Management Console access statusAttempt to access Triofox Server Agent Management Console or check if any user session is active. The vulnerability triggers when no user is logged into the console.Affected if The Management Console is accessible but no user session is active, or the console is unreachable due to crashes from prior NULL dereferences
-
Monitor for service crashesReview Windows Event Viewer application logs for crashes or access violations related to WOSCommonUtil.dll, WOSProfileMgrModule.dll, or WOSWebDavModule.dllAffected if Repeated crashes or access violation events involving the affected DLLs are logged
A system is affected if Triofox Server Agent is installed with the vulnerable DLLs and the Management Console is in a state where no user is logged in, potentially indicated by service instability or crashes.
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 dataImplement NULL pointer validation checks at every call site of WOSSysInfoGetDeviceInterface() before dereferencing the returned pointer. Ensure proper error handling when no user is logged in.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8360 — 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-8360 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