CVE-2025-26842
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 issue was discovered in Znuny through 7.1.3. If access to a ticket is not given, the content of S/MIME encrypted e-mail messages is visible to users with access to the CommunicationLog.
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 confidenceIn Znuny through 7.1.3, users without ticket access can still view the decrypted content of S/MIME encrypted emails through the CommunicationLog component. This occurs because the CommunicationLog displays encrypted email content without verifying the user has ticket-level access permissions, allowing unauthorized disclosure of sensitive encrypted communications to privileged log viewers.
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<= 7.1.3CVSS 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.1/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Znuny versionLocate the Znuny version file or admin interface that displays the current installation version. Common locations include the admin dashboard, system information page, or a version.pm file in the installation directory.Affected if The installed version is 7.1.3 or any earlier version within the 7.x branch (e.g., 7.1.2, 7.1.1, 7.0.x, etc.)
-
Confirm the CommunicationLog module is activeCheck the system configuration or module list to verify the CommunicationLog component is enabled and accessible within the Znuny installation.Affected if The CommunicationLog module is present and enabled in the system
-
Verify S/SMIME encryption is configuredExamine the Znuny email configuration settings to determine whether S/MIME encryption functionality has been enabled for email processing.Affected if S/MIME encryption is enabled and being used for email communications
-
Compare user access permissions between ticket and CommunicationLog viewsReview the role-based access control (RBAC) configuration to determine which user roles have access to the CommunicationLog component versus which roles have ticket access permissions.Affected if Users or roles exist who have access to CommunicationLog but lack corresponding ticket-level access permissions, allowing them to view decrypted email content without proper authorization
The environment is affected if running Znuny version 7.1.3 or earlier where the CommunicationLog component is accessible to users who do not have ticket access permissions, enabling unauthorized viewing of decrypted S/MIME email content.
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 dataRestrict CommunicationLog access to only display S/MIME encrypted email content for users who have been granted ticket access permissions, or implement proper authorization checks before rendering decrypted email content in the communication log view.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26842 — 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-2025-26842 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