sudo
v1.9.17 open-sourceThe section your link pointed to isn't on sudo's page any more, so we've brought you to the top.
Sudo is a program that allows a sysadmin to give limited root privileges to users and log root activity.
./configure --with-secure-path-value=no echo 'Defaults cmddenial_message="Access denied. Request access at https://helpdesk.example.com"' >> /etc/sudoers.d/denial_msg echo 'Defaults log_format=json_compact' >> /etc/sudoers.d/logging echo 'Defaults !pam_silent' >> /etc/sudoers.d/pam_output ./configure --enable-adminconf=/opt/sudo/conf sudo -Nnv && echo 'Credentials valid' || echo 'Credentials expired' # In /etc/sudoers: Defaults intercept_verify # In /etc/sudoers: Defaults log_stdin, log_stdout myuser ALL=(ALL) APPARMOR_PROFILE=\"usr.sbin.my_service\" /usr/bin/my_service Defaults intercept_type=\"ptrace\" myuser ALL=(ALL) _log_subcmds_ /bin/ls visudo -c -O root -P 0440 /etc/sudoers cvtsudoers -f /etc/sudoers -t csv > output.csv ./configure --enable-fuzzer --enable-sanitizer && make admin_flag # In /etc/sudoers or drop-in file Defaults log_format=json # In /etc/sudo_logsrvd.conf pid_file = "" sudoreplay -F <session_id> @include "/etc/sudoers.d/custom rules" # or @includedir /etc/sudoers\.d sudo -B ls sudoreplay -S <session_id> # In ldap.conf: TLS_REQCERT allow visudo /etc/sudoers.local
Summary
sudo is an open-source, free command-line tool that lets a system administrator grant limited root privileges to specific users and logs what they do with them, rather than handing out full superuser access. It runs on Linux and Unix-like systems as the sudo command invoked before another command, configured through the sudoers policy file, which makes it relevant to sysadmins and platform teams managing shared servers rather than to end users. It sits in the identity and access management space, specifically privilege escalationprivilege escalationGaining permissions beyond those an account or process initially had. It can turn limited access into administrator control or access to another user's resources. and authorization control, a role it has effectively defined rather than adopted from a peer product. First committed in 1993 and still under active development, with 81 contributors and 300 commits in the past year, it remains a maintained, current piece of core Unix infrastructure.
Sudo is a program that allows a sysadmin to give limited root privileges to users and log root activity.
How sudo helps
Which of my users can run root-level commands, and what exactly are they allowed to run?
checks the requested command against the sudoers policy file's rules for that user and host, and permits or denies based on the matching entry rather than granting blanket root access
Who ran what as root on this system, and when?
logs each escalated command with the invoking user, so past root activity can be reconstructed after the fact
Did someone try to run a command they weren't authorized for?
denies the attempt against the sudoers rules and can show the user a custom message explaining why, instead of a silent or generic failure
Is a stale root session on this machine still letting someone skip authentication?
tracks per-command timestamp entries and clears all of them across every timestamp type when credentials are invalidated, closing gaps a partial reset would leave open
Could someone escalate privileges by planting a file in the current directory?
ignores relative entries in the search path by default, so a command in the working directory cannot be substituted for a trusted one
Is the terminal a logged command actually ran from the one the audit trail claims?
resolves the real terminal device even when standard device mapping is unavailable, so the recorded session can be tied to the correct tty
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for sudo, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail sudo puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
28 entries
No entries match these filters.
- June 20251
- November 20242
- September 20241
- November 20232
- June 20232
- February 20231
- October 20221
- June 20221
- March 20221
- January 20221
- September 20211
- May 20211
- March 20211
- January 20211
- December 20201
- November 20201
- September 20201
- June 20201
- May 20201
- December 20191
- October 20192
- September 20193
Project health
Issue, contributor and maintainer activity in sudo-project/sudo, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 18 +7 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close 4 days first maintainer reply 7.1 hours
- Open backlog 38 of 287 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 38
- Contributors / month 2
- Commits / month 16
- Stars 1,710
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Articles
5 articles · updated Nov 4, 2026Where sudo turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.
Attacks on sudo 5
-
UAT-10147 Uses AI to Scale Server Attacks, Deploys SPECTRE With EDR Bypass and Linux Rootkit
…foothold, followed by abusing various known Local Privilege Escalation (LPE) exploits to escalate to root, including CVE-2022-0995 , CVE-2021-3156 , CVE-2015-5287 , CVE-2015-3246 , CVE-2010-3904 , and CVE-2022-0847 .
-
UAT-10147: Chinese-speaking adversary integrates agentic AI into post-compromise operations
CVE-2021-3156 , known as "Baron Samedit," is a heap-based buffer overflow vulnerability in the Unix sudo utility that allows any local user — even those not listed in the sudoers file — to gain root privileges without…
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.