cve.bz

CVE-2026-27851 Improper Handling of Extra Parameters

9.1 criticalEPSS 0.4%

Critical (9.1). EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-235 Improper Handling of Extra Parameters
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection, A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-27851 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-27851?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-27851?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-27851 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-27851

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-27851](https://cve.bz/cve/badge/CVE-2026-27851.svg)](https://cve.bz/cve/CVE-2026-27851)

HTML:

<a href="https://cve.bz/cve/CVE-2026-27851"><img src="https://cve.bz/cve/badge/CVE-2026-27851.svg" alt="CVE-2026-27851"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Open-Xchange GmbH OX Dovecot Prothrough 3.1.4
Open-Xchange GmbH OX Dovecot Prothrough 2.4.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13dovecot1:2.4.1+dfsg1-6+deb13u6DEBIAN-CVE-2026-27851
Debian14dovecot1:2.4.4+dfsg1-1DEBIAN-CVE-2026-27851
Ubuntu25.10dovecot1:2.4.1+dfsg1-5ubuntu4.2UBUNTU-CVE-2026-27851
Ubuntu26.04:LTSdovecot1:2.4.2+dfsg1-3ubuntu2.1UBUNTU-CVE-2026-27851
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0dovecot242.4.4-160000.1.1SUSE-SU-2026:22185-1
openSUSELeap 16.0dovecot242.4.4-160000.1.1openSUSE-SU-2026:21109-1
openSUSETumbleweeddovecot242.4.4-1.1openSUSE-SU-2026:10766-1
Alpinev3.23, v3.24dovecot2.4.4-r0ALPINE-CVE-2026-27851
Azure Linux3dovecotno fix listedAZL-86799

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This issue is classified as Important severity primarily because:

Exploitation requires a specific configuration where the safe filter is used in combination with variable expansion and subsequent pipelines on the same string during the authentication process.

Successfully bypassing the safe filter allows unsafe data to be unescaped, enabling an attacker to execute SQL or LDAP injection attacks, which can lead directly to unauthorized access and significant information disclosure.

Red Hat's mitigation

To mitigate this issue, avoid using the 'safe filter' feature in Dovecot configurations that involve variable expansion.

Administrators should review Dovecot configuration files, typically found in `/etc/dovecot/conf.d/`, to identify and disable or modify any configurations that utilize the `safe filter` with variable expansion.

A restart of the Dovecot service is necessary for these changes to take effect and may impact services relying on this feature.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10dovecotNot affected
Red Hat Enterprise Linux 6dovecotOut of support scope
Red Hat Enterprise Linux 8dovecotNot affected
Red Hat Enterprise Linux 9dovecotNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-27851.

Attack patterns (CAPEC)

  • CAPEC-460 HTTP Parameter Pollution (HPP) Severity: Medium
  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON