CVE-2026-27851: When safe filter is used with variable expansion, all following pipelines on the same string are incorrectl...
When safe filter is used with variable expansion, all following pipelines on the same string are incorrectly interpreted as safe too, enabling unsafe data to be unescaped. This can enable SQL / LDAP injection attacks when used in authentication. Avoid using safe filter until on fixed version. No publicly available exploits are known.
Security readout for executives and security teams
Plain-English summary
CVE-2026-27851 is a high-severity OX Dovecot Pro escaping flaw. A supposedly safe template filter can cause later processing on the same string to be treated as safe, allowing unsafe data to remain unescaped. In authentication paths, that may expose SQL or LDAP backends to injection risk.
Executive priority
Treat as a high-priority exposure check for mail/authentication infrastructure. Immediate urgency depends on whether your deployment uses the vulnerable safe-filter pattern and SQL or LDAP authentication. There is no cited evidence of public exploitation, but the potential authentication impact warrants prompt validation.
Technical view
The flaw involves safe filter handling with variable expansion: subsequent pipelines on the same string are incorrectly interpreted as safe. The CVSS 3.1 score is 7.4, network exploitable, no privileges or user interaction required, but high attack complexity. The cited sources associate it with CWE-235 and CWE-89.
Likely exposure
Exposure appears limited to OX Dovecot Pro deployments using the affected safe-filter pattern, especially in authentication logic touching SQL or LDAP. The affected-version data in the bundle is incomplete or ambiguous, so teams should confirm applicability against vendor and distribution advisories.
Exploitation context
The bundle states no publicly available exploits are known, and KEV is false. Do not treat this as confirmed active exploitation. Risk is still meaningful because successful exploitation could compromise confidentiality and integrity in authentication-related data flows.
Researcher notes
The source bundle gives clear vulnerability mechanics but weak affected-version detail: the affected entry lists version values of 0 and defaultStatus unaffected. Researchers should avoid broad product claims and focus validation on safe-filter plus variable-expansion behavior in OX Dovecot Pro authentication-related pipelines.
Mitigation direction
Avoid using the safe filter until running a vendor-confirmed fixed version.
Check Open-Xchange guidance for the fixed release and affected configuration details.
Review Red Hat advisories or VEX data if using packaged Dovecot components.
Prioritize remediation for systems where authentication queries use SQL or LDAP.
Monitor authentication logs for unusual query failures or account lookup anomalies.
Validation and detection
Inventory OX Dovecot Pro deployments and record exact installed versions.
Search templates/configuration for safe filter usage with variable expansion.
Identify whether those paths feed authentication, SQL, or LDAP lookups.
Compare package status against Open-Xchange and Red Hat advisory data.
Document any ambiguous version findings for vendor confirmation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-235: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-235 · source CWE mapping
Improper Handling of Extra Parameters
Improper Handling of Extra Parameters represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.