sudo-rs Allows Low Privilege Users to Discover the Existence of Files in Inaccessible Folders

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.3 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-46717: 0.37% estimated exploitation activity in the next 30 days; percentile 31.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Users with no (or very limited) sudo privileges can determine whether files exists in folders that they otherwise cannot access using sudo --list <pathname. PoC As root: As a user without any (or limited) sudo rights: I.e. the user can distinguish whether files exist. Related Original sudo (vulnerable version tested by us: 1.9.15p5) exhibited similar behaviour for files with the executable bit set. Impact Users with local access to a machine can discover the existence/non-existence of certain files, revealing potentially sensitive information in the file names. This information can also be used in conjunction with other attacks. Credits This issue was identified by sudo-rs developer Marc Schoolderman

Published by the source

13 May 2025, 14:08 UTC

Last modified by the source

13 May 2025, 14:08 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-98cv-wqjx-wx8f

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-46717

Advisory: sudo-rs Allows Low Privilege Users to Discover the Existence of Files in Inaccessible Folders
IDs: CVE-2025-46717, GHSA-98cv-wqjx-wx8f
Record: https://patchnext.com/advisories/cve-2025-46717 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sudo-rs 0.2.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io sudo-rs: affected <= 0.2.5; fixed in 0.2.6

## Suggested inspection (read-only)
- crates.io sudo-rs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sudo-rs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-98cv-wqjx-wx8f (GitHub-reviewed advisory GHSA-98cv-wqjx-wx8f lists affected ranges: crates.io sudo-rs >=0 <=0.2.5)

Commands are suggestions: review each one before running it.