Skip to main content
Menu
CVEs

Modoboa CRLF injection in relay domain DKIM selector

CVE-2026-133236Published November 19, 2026, updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fixed in 2.13.0
Who is exposed
Not reported

Summary

Modoboa has a CRLF injection flaw in the relay domain API's unvalidated dkim_key_selector field. Over the network, an attacker who must log in with high-privilege access, such as a reseller or a user with domain add or change permission, can embed a carriage return in the selector to overwrite another tenant's selector, so rspamd signs outgoing mail with a nonexistent selector and DKIM verification fails.

Written by a model

Original description

Modoboa before 2.13.0 contains a CRLF injection vulnerability that allows Resellers or users with domain add or change permission to inject rspamd DKIM selector map entries by supplying an unvalidated dkim_key_selector through the relay domain API. Attackers can embed a carriage return in the selector to override another tenant's domain selector, causing rspamd to sign its outgoing mail with a nonexistent selector and fail DKIM verification.

What to do

Upgrade to a fixed version: 2.13.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133236 (Modoboa before 2.13.0 CRLF Injection via Relay Domain dkim_key_selector), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133236 (entry last updated 2026-11-19):
Affected:
- PyPI package modoboa: fixed in 2.13.0
Fixed versions: 2.13.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133236 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133236 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/modoboa/modoboa/security/advisories/GHSA-p68v-69qc-9345
- https://github.com/modoboa/modoboa/commit/b4550be1d4a058fd6f967b806afcce36912757a8
- https://github.com/modoboa/modoboa/releases/tag/2.13.0
- https://github.com/modoboa/modoboa/blob/2.12.0/modoboa/relaydomains/api/v1/serializers.py#L36-L55
- https://github.com/modoboa/modoboa/blob/2.12.0/modoboa/rspamd/jobs.py#L78-L83
- https://github.com/modoboa/modoboa
- https://www.vulncheck.com/advisories/modoboa-before-2.13.0-crlf-injection-via-relay-domain-dkim-key-selector
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133236
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133236"}.

Affected versions

cve.now Index

18Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects PyPI packages
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 37 if advisories confirm default setups are exposed

Impact

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 9

Questions about CVE-2026-133236

Is CVE-2026-133236 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133236?

modoboa (PyPI): before 2.13.0.

Source: cve.now feed data

How do I fix CVE-2026-133236?

Upgrade to a fixed version: 2.13.0.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.