# CVE-2026-113598: Modoboa before 2.8.0 IDOR via API v2 alarms bulk_delete


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-cq85-78wv-p3mx

## What is CVE-2026-113598?

CVE-2026-113598 is a medium-severity vulnerability in modoboa, published on 20 Oct 2026. 

### Official description

Modoboa before 2.8.0 contains an insecure direct object reference vulnerability that allows authenticated users to delete alarms of other domains via the POST /api/v2/alarms/bulk_delete/ action. Attackers can enumerate sequential alarm IDs to delete DNS, MX and blocklist monitoring alarms server-wide, hiding problems from responsible administrators.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

No fix has been published for CVE-2026-113598 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-113598 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: modoboa. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-113598/ (Markdown: https://insights.sbomify.com/CVE-2026-113598/index.md)
```

## Sources

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

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