Sudo Project vulnerabilities2 known to be exploited.

Vendor2 known exploited
The short answer

Sudo Project has 23 published vulnerabilities across 1 product in our catalogue. 2 of them are on the list of flaws known to be exploited, so criminals are using them now. The most affected product is Sudo, with 23. If you run Sudo Project software, patch the exploited flaws first.

See the exploited flaws

The most recent Sudo Project flaw added to the known-exploited list is CVE-2025-32463, on 29 September 2025. We keep watching the known-exploited list.

Products

Which Sudo Project products have the most vulnerabilities?

Sudo leads with 23 published vulnerabilities. Open a product to see its versions and which of its flaws criminals are already using.

  1. Sudo23
Published vulnerabilities
Known exploited

Which Sudo Project vulnerabilities are being exploited?

2 flaws are on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.3
    CVE-2025-32463CriticalKnown exploited
    Sudo Inclusion of Functionality from Untrusted Control Sphere Vulnerability

    Sudo contains an inclusion of functionality from untrusted control sphere vulnerability.

    Chance of use55%Known exploited since29 Sep 2025
  2. 7.8
    CVE-2021-3156HighKnown exploited
    Sudo Heap-Based Buffer Overflow Vulnerability

    Sudo contains an off-by-one error that can result in a heap-based buffer overflow, which allows for privilege escalation.

    Chance of use>99%Known exploited since6 Apr 2022
Exploit likelihood

Which Sudo Project flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2021-3156HighKnown exploited

    Sudo before 1.9.5p2 contains an off-by-one error that can result in a heap-based buffer overflow, which allows privilege escalation to root via "sudoedit -s" and a command-line argument that ends with a single...

    CVSS7.8Published26 Jan 2021
  2. 64%

    In Sudo before 1.8.28, an attacker with access to a Runas ALL sudoer account can bypass certain policy blacklists and session PAM modules, and can cause incorrect logging, by invoking sudo with a crafted user ID.

    CVSS8.8Published17 Oct 2019
  3. 55%
    CVE-2025-32463CriticalKnown exploited

    Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option.

    CVSS9.3Published30 Jun 2025
  4. 55%

    In Sudo before 1.9.12p2, the sudoedit (aka -e) feature mishandles extra arguments passed in the user-provided environment variables (SUDO_EDITOR, VISUAL, and EDITOR), allowing a local attacker to append arbitrary...

    CVSS7.8Published18 Jan 2023
  5. 19%

    In Sudo before 1.8.26, if pwfeedback is enabled in /etc/sudoers, users can trigger a stack-based buffer overflow in the privileged sudo process.

    CVSS7.8Published29 Jan 2020
  6. 8.0%

    Todd Miller's sudo version 1.8.20 and earlier is vulnerable to an input validation (embedded spaces) in the get_process_ttyname() function resulting in information disclosure and command execution.

    CVSS6.4Published5 Jun 2017
  7. 4.5%

    Sudo before 1.9.17p1, when used with a sudoers file that specifies a host that is neither the current host nor ALL, allows listed users to execute commands on unintended machines.

    CVSS2.8Published30 Jun 2025
  8. 1.7%

    Sudo before 1.9.13p2 has a double free in the per-command chroot feature.

    CVSS7.2Published28 Feb 2023
  9. 1.5%

    sudoedit in Sudo before 1.8.15 allows local users to gain privileges via a symlink attack on a file whose full path is defined using multiple wildcards in /etc/sudoers, as demonstrated by "/home/*/*/file.txt."

    CVSS7.2Published17 Nov 2015
  10. 1.2%

    Sudo before 1.6.6 contains an off-by-one error that can result in a heap-based buffer overflow that may allow local users to gain root privileges via special characters in the -p (prompt) argument, which are not...

    CVSS7.8Published16 May 2002
Every product

All Sudo Project products we track.

1 products, most vulnerabilities first. Find the ones you run, then open a product to see its versions and exploited flaws.

Precursor Intelligence

Running Sudo Project? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

Our catalogue lists 23 published vulnerabilities across 1 product and 84 versions from Sudo Project. The most recent Sudo Project flaw added to the known-exploited list is CVE-2025-32463, on 29 September 2025.

2 Sudo Project vulnerabilities are on the list of flaws known to be exploited. The most recently added are CVE-2025-32463 and CVE-2021-3156. The full list is on this page.

Sudo, with 23 published vulnerabilities. Its own page lists the ones known to be exploited.

Create a Precursor Intelligence account and track the Sudo Project products you run. We match them against every published flaw, give each one a risk score from 0 to 100 and tell you as soon as we spot one that affects you, by email, in the app or by webhook.