Medium Injection

CVE-2026-93635 — Zimbra Collaboration Suite LDAP Filter Injection via Unescaped computeDn() Template Substitution

LDAP filter injection in Zimbra Collaboration Suite 10.1.0 through 10.1.21 allows unauthenticated attackers to alter external LDAP search filters. On domains using search-filter authentication and lazy provisioning, this creates a password oracle for external directory users. Authenticated S/MIME lookups can also return certificates and identity data for unintended directory entries.

Published Oct 14, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: rapid7

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.2% (30-day exploitation probability)+2
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.22%

ahead of 11% of scored CVEs · Oct 15, 2026

Affects

Zimbra

Zimbra Collaboration Suite

CVSS base

5.3

Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Zimbra Zimbra Collaboration Suite).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Zimbra	Zimbra Collaboration Suite	≤ 10.1.21	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
5.3	CVSS 3.1	Medium	3.9	1.4	cve@rapid7.com via NIST National Vulnerability Database
5.3	CVSS 3.1	Medium	—	—	rapid7 via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N (score shown at the top: cve@rapid7.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-90 · LDAP Injection

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Look for parameters with command/query metacharacters and unexpected child processes of the service.

web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · zimbra/zimbra collaboration suite
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 14, 2026
CVSS changed · 5.3
Oct 14, 2026 · NIST National Vulnerability Database
Source status changed · → Received
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
CVE published
Oct 14, 2026 · rapid7

Source activity

Repeated readings are counted rather than listed.

1× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

1 on the record

www.rapid7.com/blog/post/ve-breaking-zimbra-identity-boundaries-part-1
third-party-advisory, NIST National Vulnerability Database

Elsewhere on this site

Zimbra
every CVE for this vendor

Injection
same class

CWE-90
other pages naming this weakness

Related CVEs (same products)

Low CVE-2026-93637 Zimbra Collaboration Suite GraphQL Batched Authentication Bypasses Pre-Auth Rate Limiting 1d
Medium CVE-2026-50055 Zimbra Collaboration Suite Sieve Notify Filter Action Bypasses Mail Forwarding Restriction via Variable Expansion 7d
High CVE-2026-50054 Zimbra Collaboration Suite GrantRightsRequest SOAP Handler Allows Self-Granting of Undocumented loginAs Mailbox Delegation Right 7d
Medium CVE-2026-10631 Zimbra Collaboration Suite EWS Extension Authorization Bypass via Crafted Composite Folder/Item Identifier 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No CISA SSVC assessment.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-93635 is "Zimbra Collaboration Suite LDAP Filter Injection via Unescaped computeDn() Template Substitution", rated Medium. It affects Zimbra Collaboration Suite (Zimbra); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.