# CVE-2026-133236: Modoboa before 2.13.0 CRLF Injection via Relay Domain dkim_key_selector


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 19 Nov 2026
- **Also known as:** GHSA-fc6q-jjw3-255x, GHSA-p68v-69qc-9345

## What is CVE-2026-133236?

CVE-2026-133236 is a medium-severity vulnerability in modoboa, published on 19 Nov 2026. 

### Official 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.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

## Which versions are affected by CVE-2026-133236?

1 open source package ship an affected version, including modoboa.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `modoboa` | PyPI | `pkg:pypi/modoboa` | All versions | 2.13.0 |

## How do I fix CVE-2026-133236?

Upgrade modoboa to 2.13.0 or later.

## Is CVE-2026-133236 being exploited?

There is no known exploitation of CVE-2026-133236 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-133236 and fix it if it is affected.

What it is: CVE-2026-133236 is a medium-severity vulnerability in modoboa, published on 19 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-133236 in the wild and no public exploit code.

Affected packages and fixed versions:
- modoboa (PyPI): affected all versions; fixed in 2.13.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-133236/ (Markdown: https://insights.sbomify.com/CVE-2026-133236/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-133236
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-133236
- OSV: https://osv.dev/vulnerability/CVE-2026-133236

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-133236/
Summaries are generated and may contain mistakes; the official description above is the record.
