{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-33586 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33586 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33586 is a medium-severity vulnerability in OVHcloud, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33586 and fix it if it is affected.\n\nWhat it is: CVE-2026-33586 is a medium-severity vulnerability in OVHcloud, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33586 in the wild and no public exploit code.\n\nAffected product: OVHcloud. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33586/ (Markdown: https://insights.sbomify.com/CVE-2026-33586/index.md)","id":"CVE-2026-33586","markdown":"https://insights.sbomify.com/CVE-2026-33586/index.md","name":"CVE-2026-33586","record":{"aliases":["GHSA-rpc3-43rh-hpm4"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OVH mail server","requires_auth":"low_privilege","summary":"Authenticated users can forge sender addresses to impersonate any OVH-hosted domain, bypassing SPF validation due to default mail server configurations.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ENISA","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"},{"id":"CWE-290","name":"Authentication Bypass by Spoofing"},{"id":"CWE-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"Authenticated users are able to manipulate both the SMTP\nenvelope “Envelope-from” and “From” fields when sending\nemails through OVH mail servers.\n\nDue to OVH's default SPF configuration, which\ncommonly includes include:mx.ovh.com, any authenticated user with a\nvalid OVH email account can send messages that appear to originate from any\nOVH-hosted domains using the default SPF record. Since the SPF policy\nexplicitly authorizes OVH mail servers (mx.ovh.com) to send mail on behalf of\nthese domains, forged messages successfully pass SPF validation despite\nnot being authorized by the impersonated domain owner.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Authenticated SMTP Sender Address Forgery","id":"CVE-2026-33586","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Remote Code Execution (RCE) via Server-Side Template Injection (SSTI)","id":"CVE-2026-33587"},"packages":[],"prev":{"headline":"Arqit SKA-Platform Improper Handling of Parameters Vulnerability","id":"CVE-2026-33585"},"products":["OVHcloud"],"published":"2026-10-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-07","vendors":["OVHcloud"]},"summary":"Authenticated users can forge sender addresses to impersonate any OVH-hosted domain, bypassing SPF validation due to default mail server configurations.","url":"https://insights.sbomify.com/CVE-2026-33586/"}