← Back to results
Vulnerability record · public intelligence
CVE-2023-26430
LOW

CVE-2023-26430

Published Aug 2, 2023 · Updated Oct 23, 2026

Severity · CVSSLOW · 3.5
Known exploitationNot listed
EPSS / likelihood0.75%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Oct 23, 2026

Attackers with access to user accounts can inject arbitrary control characters to SIEVE mail-filter rules. This could be abused to access SIEVE extension that are not allowed by App Suite or to inject rules which would break per-user filter processing, requiring manual cleanup of such rules. We have added sanitization to all mail-filter APIs to avoid forwardning control characters to subsystems. No publicly available exploits are known.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

Attackers with access to user accounts can inject arbitrary control characters to SIEVE mail-filter rules. This could be abused to access SIEVE extension that are not allowed by App Suite or to inject rules which would break per-user filter processing, requiring manual cleanup of such rules. We have added sanitization to all mail-filter APIs to avoid forwardning control characters to subsystems. No publicly available exploits are known.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDEPSS
SSVC priority
LOW
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. software.open-xchange.com ↗
  2. Security advisory ↗
  3. seclists.org ↗
  4. packetstormsecurity.com ↗

Record history

Published Aug 2, 2023 · Last refreshed Oct 23, 2026