# CVE-2026-44931: malcontent: Disk Space Exhaustion via Globally Accessible D-Bus API

> An attacker can exhaust disk space via a globally accessible D-Bus API in malcontent, causing denial of service on Linux systems.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-9jrh-5pwj-wfmp, UBUNTU-CVE-2026-44931

## What is CVE-2026-44931?

CVE-2026-44931 is a medium-severity denial of service vulnerability in gnome malcontent, published on 13 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The newly introduced  RecordUsage D-Bus method https://gitlab.freedesktop.org/pwithnall/malcontent/-/blob/0.14.0/libmalcontent-timer/child-timer-service.c  in
malcontent-timerd allows arbitrary users in the system to slowly fill up disk space
in /var/lib/malcontent-timerd

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-44931 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-44931 is a medium-severity denial of service vulnerability in gnome malcontent, published on 13 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44931 in the wild and no public exploit code.

Affected product: gnome malcontent. 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-44931/ (Markdown: https://insights.sbomify.com/CVE-2026-44931/index.md)
```

## Sources

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

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