dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-2493

HIGH · 7.5 CVSS v3.0 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
IceWarp collaboration Directory Traversal Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information on affected installations of IceWarp. Authentication is not required to exploit this vulnerability. The specific flaw exists within handling of the ticket parameter provided to the collaboration endpoint. The issue results from the lack of proper validation of a user-supplied path prior to using it in file operations. An attacker can leverage this vulnerability to disclose information in the context of root. Was ZDI-CAN-25440.

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 confidence

IceWarp collaboration feature contains a path traversal vulnerability in the ticket parameter handling of the collaboration endpoint. The application fails to validate user-supplied paths before file operations, allowing unauthenticated attackers to use '..' sequences to access arbitrary files on the system. Since the service runs as root, attackers can read sensitive system files.

MitigationImplement strict input validation on the ticket parameter to reject path traversal sequences ('..'). Validate that the requested path remains within the intended directory. Consider running the service with limited privileges rather than root.

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
None
Availability
None

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

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

  1. Verify IceWarp is installed
    Look for IceWarp processes, services, or installation directories on the system (common paths include /opt/icewarp, /usr/local/icewarp, or run 'ps' to find icewarp processes)
    Affected if IceWarp software is present on the system
  2. Confirm collaboration endpoint is accessible
    Check IceWarp web configuration or access logs for the collaboration feature endpoint (typically responds at a path containing 'collaboration' or 'ticket' in the URL structure)
    Affected if The collaboration endpoint is enabled and reachable
  3. Determine installed IceWarp version
    Locate IceWarp version information in installation directories, configuration files, or via version command-line tools provided by IceWarp, then compare against the affected version range
    Affected if Installed version falls within the vulnerable version range (if known) or is an unpatched release
  4. Check service execution context
    Examine the IceWarp service process ownership (run 'ps aux | grep icewarp' or check service configuration) to determine if it runs as root
    Affected if Service runs as root (escalates impact but vulnerability exists regardless)
  5. Test for path traversal exposure
    Send a benign request to the collaboration endpoint with a ticket parameter containing '..' sequences (e.g., ?ticket=..%2F..%2Fetc%2Fpasswd) and observe if the application processes or rejects the path traversal
    Affected if Application accepts and processes path traversal sequences in the ticket parameter

The environment is affected if IceWarp is installed with the collaboration feature enabled and the installed version matches vulnerable releases, regardless of whether the service runs as root.

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

Implement strict input validation on the ticket parameter to reject path traversal sequences ('..'). Validate that the requested path remains within the intended directory. Consider running the service with limited privileges rather than root.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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