dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-8811

HIGH · 7.1 CVSS v4.0 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
SEPPmail versions before 15.0.5 allow improper handling of attachment filenames during encrypted PDF generation. An attacker can exploit this to create new files outside the intended directory, potentially placing files in web-accessible locations.

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

SEPPmail versions before 15.0.5 contain a path traversal vulnerability in the encrypted PDF generation feature. Attackers can manipulate attachment filenames to escape the intended directory and write files to arbitrary locations on the server, potentially including web-accessible directories.

MitigationUpgrade SEPPmail to version 15.0.5 or later to obtain the patched code that properly validates and sanitizes attachment filenames before writing files.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify SEPPmail version
    Locate the SEPPmail installation and check its version number. Common methods include: checking the admin interface version display, reviewing installation logs, or querying the application directly via its management interface.
    Affected if The installed version is below 15.0.5 (for example, 15.0.4, 14.x, or earlier)
  2. Confirm encrypted PDF feature is active
    Determine whether the encrypted PDF generation feature is enabled on the SEPPmail server. This may be accessible through the admin configuration panel, email processing rules, or documented as part of the deployment.
    Affected if The encrypted PDF generation feature is enabled and accessible to users or processes that handle email attachments
  3. Verify file write permissions
    Review the file system permissions on the SEPPmail server, particularly directories where the PDF generation feature writes output. Check if the application process has write access to web-accessible directories.
    Affected if The service account running SEPPmail has write permissions to web-accessible document root or web directories
  4. Inspect for anomalous files
    Search the web-accessible directories (such as web roots, upload folders, or static content directories) for unexpected files, especially executable scripts or documents with unusual timestamps that correlate with PDF processing activity.
    Affected if Unexpected files exist in web-accessible directories that were not intentionally placed there, particularly files with recent modification dates

You are affected if SEPPmail version is below 15.0.5 AND the encrypted PDF generation feature is enabled and accessible on your server.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SEPPmail to version 15.0.5 or later to obtain the patched code that properly validates and sanitizes attachment filenames before writing files.

Recommended fix Moderate confidence

SEPPmail 15.0.5 or later

  1. Identify the current SEPPmail version installed in your environment
  2. Download SEPPmail version 15.0.5 or later from the official vendor repository (downloads.seppmail.com)
  3. Review the upgrade documentation provided by SEPPmail before initiating the update
  4. Perform the upgrade following the vendor's recommended procedure
  5. Verify that the upgrade was successful and the new version is running
  6. Test the encrypted PDF generation functionality to confirm the path traversal vulnerability is remediated
Caveat Review vendor release notes for any changes to encrypted PDF generation functionality or configuration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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