ABRT · CVE-2026-110330 · Other
NO FIX YET
abrt-server trusts a PID supplied by the client when creating problem dumps over abrt.socket, and as root copies that process's /proc data, including its environment, into a directory the unprivileged caller owns. A local attacker can read environment variables and metadata from other users' or root's processes while abrtd runs.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems where the abrt crash-reporting service (abrtd and abrt.socket) is installed and running, so that local users can submit dump requests. Machines without abrt are not exposed. The sources do not give the affected version range or a fixed version.
Not affected if abrt-not-installed, abrtd-not-running
Who cares abrt, linux, self-hosted
systemctl status abrtdabrt-cli --version or your package managerNo fix yet, per the sources.
A flaw was found in abrt. abrt-server trusts a client-supplied PID when creating problem dumps over abrt.socket and, running as root, copies that process's /proc data (including environ) into a dump directory owned by the connecting unprivileged user. This allows a local attacker to read environment variables and related metadata of other users' or root processes when abrtd is running.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.