A information rumor successful Omarchy’s default Docker configuration meant that essentially each programme moving successful the user’s desktop convention could escalate to guidelines without a password, sudo, aliases a privilege prompt.
If you usage Omarchy, the astir important takeaway is simple: update to 4.0.1.
I reported this rumor privately done the project’s responsible-disclosure process. The underlying configuration has since been patched, truthful I’m publishing the specifications now to explicate what the rumor is and fto users cognize to update their systems.
The Issue
Omarchy configured its default personification arsenic a personnel of the Linux docker group.
That allows users to tally commands specified as:
without typing sudo.
On arch the Docker daemon runs arsenic guidelines and listens on:
Members of the docker group tin pass pinch that socket. Docker itself explicitly warns that the docker group grants root-level privileges to the user.
A process pinch entree to the Docker socket tin inquire the root-owned Docker daemon to motorboat a instrumentality arsenic root, equine arbitrary portions of the big filesystem into it, run connected those files arsenic root, and tally codification arsenic root.
On affected Omarchy systems, this intends that the default personification and each processes launched successful that personification convention person entree to root.
Proof of Concept
On a caller affected Omarchy installation effort reference /etc/shadow:
Now observe the group memberships for your user:
Now publication the protected record pinch docker acting arsenic root:
The bid is launched by an mean personification process, but the existent filesystem access is performed done a daemon moving arsenic root.
Scope
Linux supplementary groups are inherited by kid processes truthful this affects the entire personification session.
Walking the process character beneath the user’s systemd --user lawsuit showed the Docker group coming connected fundamentally each normal process successful the session.
This intends astir each process wherever untrusted codification could run, could obtain root, including:
- AI coding agents and supplier harnesses
- web browsers
- editors and IDEs
- npm scripts
- random improvement tools
- background processes
In different words, a discuss of a normal personification exertion could immediately become a afloat instrumentality compromise.
Security Defaults
There is different important facet of this configuration. It was opt-out, not opt-in. A personification did not person to really usage Docker. The information tradeoff was made for them, applied to the default account, and the tradeoff was not explained to the user.
Security-sensitive defaults matter precisely because galore users reasonably assume that the operating strategy defaults to unafraid and will pass aliases prompt them to opt-in to little unafraid settings.
Misleading Documentation
Omarchy did mention the Docker group successful its development-tools documentation:
Omarchy installs everything needed to tally [docker] well. This includes […] the personification group changes needed for you to tally Docker arsenic the normal personification and not arsenic root.
The information accusation is almost the other of what a emblematic scholar might infer from “not arsenic root”. A personification reference that explanation could reasonably conclude that Omarchy had configured Docker successful immoderate benignant of rootless mode. It had not.
Impacted Versions
This affects versions anterior to 4.0.1. I tested it connected the latest 3.x iso (3.8.4) and it was besides impacted.
Timeline
The timeline of commits from the preamble to solution of this issue:
- June 1, 2025 — Docker group rank introduced 25799ee
- June 2, 2025 — Docker group summation temporarily abnormal c5ee230
- June 17, 2025 — Docker group rank re-enabled fdd2aaf
- August 24, 2026 — Docker group rank removed from the default configuration b5ded31
The Broader Context
As AI is progressively producing precocious severity CVEs against halfway infrastructure, security needs to beryllium apical of mind for each developers, but particularly authors of distributions targeted astatine developers. Lately location person been innumerable reports of developer machines being compromised and their entree utilized to contaminate the package proviso concatenation aliases utilization accumulation systems. Developers are high-value targets because of the level of entree they are often granted. Developer machines typically disable information guardrails for convenience, store credentials successful plain-text dotfiles, and accumulate entree to systems. This must change.
I’m judge this was conscionable an oversight by DHH not knowing the implications of adding the docker group. No distribution is going to make cleanable decisions when it comes to security. I was amazed by the velocity of consequence to this issue being reported which is simply a patient sign.
That said, this isn’t the first clip I person ran into information issues with Omarchy and frankly I do not spot the determination making process arsenic it stands to ensure the level of information I expect retired of my distro. I dream that changes at some constituent because location is simply a batch to for illustration astir Omarchy.
Podman
If you are a personification of Docker connected Linux and don’t want to beryllium forced into granting root (even pinch sudo) to tally containers, past I highly urge you effort out Podman. Podman is daemonless. Your containers tally as normal kid processes successful their ain personification namespaces and don’t require immoderate sort of guidelines access. I person been moving Podman for galore months now and it has entirely replaced each of my Docker workflows. I highly urge giving it a try.
References
- Docker: Manage Docker arsenic a non-root user
- Omarchy Docker documentation
English (US) · 
Indonesian (ID) · 
