Skip to content

CVE-2023-22809

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 entries to the list of files to process. This can lead to privilege escalation. Affected versions are 1.8.0 through 1.9.12.p1. The problem exists because a user-specified editor may contain a "--" argument that defeats a protection mechanism, e.g., an EDITOR='vim -- /path/to/extra/file' value.

CVSS
7.8Highscored by CISA
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
55.4%chance of exploitation in the next 30 daystop 1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
18 Jan 2023analysed here 12 Nov 2026

Summary

Triage

Exploitable
At runtime
Attack vector
local
Weakness
  • CWE-269 Improper Privilege Management
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • sudo_project:sudo
  • debian:debian_linux
  • fedoraproject:fedora
  • apple:macos

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 on Exploit-DB · 1 Metasploit module · 12 GitHub proofs of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 4 Apr 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 18 Jan 2023Published
  2. 21 Jan 2023First public exploit or proof of concept2 days later
  3. 4 Apr 2025CISA SSVC assessment: exploitation none805 days (about 2 years) later
  4. 4 Apr 2025CVE record last updatedsame day later
  5. 12 Nov 2026Analysed by vulneraibility.com587 days (about 2 years) later

CVSS vector

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

MetricValueWhat it means
Attack vectorLocalLocal access required (shell, logged-in user).
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredLowThe attacker needs basic user privileges.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2023-22809 being exploited?

Not confirmed. CVE-2023-22809 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 55% probability of exploitation in the next 30 days.

How severe is CVE-2023-22809?

CVE-2023-22809 is rated High with a CVSS score of 7.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-22809?

Yes. A fix has been recorded for CVE-2023-22809. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-22809 affect?

CVE-2023-22809 affects sudo_project:sudo, debian:debian_linux, fedoraproject:fedora, apple:macos. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

14 references in the CVE record, grouped by the tags the record gives them.

Advisories (4)

Other links (10)

Show 4 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com