CVE-2026-33586

Authenticated SMTP Sender Address Forgery

Published Oct 7, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Authenticated users are able to manipulate both the SMTP
envelope “Envelope-from” and “From” fields when sending
emails through OVH mail servers.



Due to OVH's default SPF configuration, which
commonly includes include:mx.ovh.com, any authenticated user with a
valid OVH email account can send messages that appear to originate from any
OVH-hosted domains using the default SPF record. Since the SPF policy
explicitly authorizes OVH mail servers (mx.ovh.com) to send mail on behalf of
these domains, forged messages successfully pass SPF validation despite
not being authorized by the impersonated domain owner.

Analysis

AI-generated

Technical impact

Authenticated users of OVH email accounts can change the SMTP envelope‑from and From header values when sending mail through OVH’s servers. Because the default SPF record for many OVH‑hosted domains includes the server at mx.ovh.com, these forged messages are treated as legitimate and pass SPF validation, even though they are not authorized by the domain owner. The vulnerability enables attackers to impersonate any domain hosted on OVH, facilitating phishing and spam distribution that can deceive recipients and defeat standard email authentication checks.

Affected Systems

OVHcloud’s mail services for all domains hosted on OVH, particularly those that use the default SPF record with include:mx.ovh.com, are affected. The problem arises for every authenticated user with an OVH email account who can set the envelope‑from From fields when sending messages. No version or patch information is available in the CVE entry.

Risk and Exploitability

With a CVSS score of 6.3 the issue is moderate severity, and it is not currently listed as a known exploited vulnerability in CISA KEV. The exploitation requires a valid authenticated account, so the attack vector is internal based on the description. Although the vulnerability does not allow arbitrary code execution, the ability to forge sender addresses undermines trust mechanisms and enables phishing campaigns, which could lead to financial loss or brand damage if the spoofed emails are not detected.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Disable or modify the default SPF record so that it does not include mx.ovh.com for domains where the server should not be authorized to send mail on behalf of the domain.
  • Revoke or limit the ability for authenticated users to set or edit the Envelope‑from and From header values on outgoing mail.
  • Enforce additional authentication mechanisms such as DKIM signing and DMARC with a reject or quarantine policy to detect and block spoofed messages.
  • Monitor outbound email for forged sender fields and apply logging to detect abuse.

Generated by OpenCVE AI on October 7, 2026 at 17:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Ovhcloud
Ovhcloud ovhcloud
Vendors & Products Ovhcloud
Ovhcloud ovhcloud
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Authenticated users are able to manipulate both the SMTP envelope “Envelope-from” and “From” fields when sending emails through OVH mail servers. Due to OVH's default SPF configuration, which commonly includes include:mx.ovh.com, any authenticated user with a valid OVH email account can send messages that appear to originate from any OVH-hosted domains using the default SPF record. Since the SPF policy explicitly authorizes OVH mail servers (mx.ovh.com) to send mail on behalf of these domains, forged messages successfully pass SPF validation despite not being authorized by the impersonated domain owner.
Title Authenticated SMTP Sender Address Forgery
Weaknesses CWE-1188
CWE-290
CWE-346
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:N/E:A'}

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

  • CWE-290

    Authentication Bypass by Spoofing

  • CWE-346

    Origin Validation Error

Sources

Status
PUBLISHED
Assigner
ENISA
Published
Updated
Oct 7, 2026, 8:27 PM
Reserved
Mar 23, 2026, 12:53 PM
Status
Awaiting Analysis
Published
Oct 7, 2026, 4:17 PM
Modified
Oct 8, 2026, 9:33 PM