Security readout for executives and security teams
Plain-English summary
A safety marker in OX Dovecot Pro can be applied too broadly after variable expansion. Data that should be escaped may be treated as safe, creating a path to SQL or LDAP injection, especially around authentication logic.
Executive priority
Treat as high priority if OX Dovecot Pro is used for authentication with SQL or LDAP. The risk is serious, but urgency is moderated by high attack complexity and no cited public exploitation.
Technical view
When the safe filter is used with variable expansion, later pipelines on the same string are incorrectly interpreted as safe. The CVSS 3.1 score is 7.4 with network attack vector, high complexity, no privileges, no user interaction, and high confidentiality and integrity impact.
Likely exposure
Exposure appears limited to OX Dovecot Pro deployments using the safe filter with variable expansion in strings that later feed SQL or LDAP operations. The provided data does not identify concrete affected version ranges beyond the vendor/product listing.
Exploitation context
The bundle says no publicly available exploits are known, and KEV status is false. Exploitation would depend on a vulnerable template/data-flow pattern where untrusted input reaches SQL or LDAP authentication logic after being incorrectly marked safe.
Researcher notes
Evidence is incomplete on exact affected versions and fixed releases. The key validation task is finding unsafe safe-filter usage in authentication-related string processing, then matching deployments against vendor CSAF and Red Hat records.
Mitigation direction
- Avoid using the safe filter until running a fixed version.
- Review Open-Xchange guidance for fixed versions and supported remediation.
- Prioritize authentication paths that use SQL or LDAP backends.
- Apply vendor updates when a fixed release is confirmed.
- Track Red Hat and Open-Xchange advisories for status changes.
Validation and detection
- Inventory OX Dovecot Pro deployments and versions.
- Search templates or configuration for safe filter plus variable expansion.
- Trace whether affected strings feed SQL or LDAP authentication flows.
- Confirm installed versions against vendor advisory data.
- Review authentication logs for unusual SQL, LDAP, or login failures.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-89: Database access and collection lookup
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.
Open ATT&CK lookupCVE-2026-27851 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2OXCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N2.25.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Base CVSS 3.1 score
7.4HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-05-12T14:01:35.826Z: Reported to Red Hat.
- 2026-05-12T13:28:43.846Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://documentation.open-xchange.com/dovecot/security/advisories/csaf/2026/oxdc-adv-2026-0002.jsonCVE reference, OX · vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-27851CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2476471CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-27851.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.