Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged local macOS user
-
DeliveryInitiate ABR privilege elevation session
-
ExploitIdentify unsanitized input path in ABR elevation workflow
-
ExecutionInject malicious sudoers entry via crafted input
-
PersistSudoers file written with persistent root grant
-
ImpactExecute sudo commands as root after ABR session ends
Vulnerability Assessment
| Weakness |
CWE
|
| Exploitation Conditions | Exploitation requires the attacker to have a standard (low-privileged) local user account on a macOS system with Admin By Request installed and running. The high attack complexity (AC:H) reflects that exploitation must occur during an active ABR privilege elevation session - the attacker must reach a specific input path within ABR's workflow where user-supplied data is processed and written to the sudoers file without adequate sanitization. Remote exploitation is not possible (AV:L); the attacker must be locally authenticated to the macOS endpoint. What limits exploitation: the attack cannot be performed remotely; the attacker must understand ABR's internal elevation flow sufficiently to identify and reach the vulnerable input point; and AC:H implies specific timing or configuration conditions beyond simply having a session open. Authentication requirements are confirmed by CVSS PR:L - a valid low-privileged local account is required. |
| Impact | The CVSS 3.1 base score of 7.8 with vector AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H reflects the attack's local-only reach, elevated complexity (requires an active ABR session and a specific input injection path), and transformative impact: persistent root on the host after session termination. Scope:Changed correctly captures that the compromise extends beyond ABR itself to the underlying macOS system via sudoers. No EPSS score is available in the provided data, and the vulnerability is not in CISA KEV, so no confirmed widespread exploitation exists at time of analysis. No public proof-of-concept is referenced. The real-world risk is context-dependent: environments deploying ABR specifically to restrict admin rights on macOS endpoints face a scenario where a determined low-privileged user can permanently undo those controls - making this a direct bypass of the security product's core function. The AC:H rating (high complexity) is a meaningful mitigating signal: exploitation is not trivial and requires understanding ABR's internal elevation workflow. However, for insider threat or post-initial-access scenarios, the payoff (persistent, unrestricted root) makes the effort worthwhile. No CVSS/description conflict identified. |
| Exploit ScenarioDerived | A standard macOS user on a corporate endpoint initiates a legitimate ABR privilege elevation request and, during the session input phase, supplies a crafted string that ABR writes without sanitization into the sudoers file - for example, appending a rule granting themselves NOPASSWD root for all commands. After the ABR session expires and the temporary elevation is revoked, the injected sudoers entry remains intact, giving the user persistent, unrestricted root access via sudo without further interaction. No public proof-of-concept exploit has been identified at time of analysis, but the attack is mechanically straightforward for someone who understands ABR's elevation input handling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Persistent root escalation in Admin By Request (ABR) on macOS allows a low-privileged local user to inject malicious entries into the sudoers file during an ABR privilege elevation session, achieving root access that outlasts the session itself. The flaw is tracked under advisory ABR-MAC-26-02 and was flagged by Singapore's Cyber Security Agency (CSA). No public exploit or CISA KEV listing is present at time of analysis, but the nature of the impact - permanent, session-independent privilege escalation - makes this high priority for any enterprise fleet running ABR on macOS.
RemediationAI
Consult the vendor security advisory at https://docs.adminbyrequest.com/security-advisories/abr-mac-26-02.htm for the patched ABR macOS agent version and apply it immediately; the input data does not specify an exact fixed version number, so the advisory is the authoritative source. Until patching is complete, restrict which users are permitted to initiate ABR elevation sessions - reducing the pool of principals who can trigger the vulnerable input path limits exposure. Audit /etc/sudoers and /etc/sudoers.d on all macOS endpoints running ABR for unexpected entries, particularly NOPASSWD rules not placed by ABR or administrators, as these would indicate prior exploitation. Enabling macOS System Integrity Protection (SIP) in its strictest configuration provides some defense-in-depth against unauthorized sudoers modifications, though it may not fully block a process running with elevated context. No workaround fully substitutes for the vendor patch given that the flaw is in ABR's core elevation workflow.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Admin By Request (ABR) is an endpoint privilege management (EPM) solution that allows standard users to temporarily elevate privileges for approved tasks without granting persistent admin rights. The CPE string (cpe:2.3:a:admin_by_request_(abr):admin_by_request_(abr):*:*:*:*:*:*:*:*) covers all versions with a wildcard, indicating the affected version range is not precisely bounded in NVD. The advisory URL suffix 'abr-mac-26-02' confirms this is the macOS agent. The root cause is insufficient input validation (tagged as Code Injection) during the ABR elevation workflow: ABR fails to sanitize user-supplied input before it is written to or used to construct entries in /etc/sudoers or sudoers.d. The sudoers file governs sudo access on Unix/macOS systems; a malicious entry - e.g., granting NOPASSWD ALL to the attacker's user - persists on disk after the ABR session terminates. No CWE was formally assigned, but CWE-20 (Improper Input Validation) and CWE-94 (Code Injection) align with the described mechanism and the 'Code Injection' tag.
Know when Admin By Request Abr gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Local-only attack during an active ABR session (AC:H); low-privilege account required (PR:L); scope changes to host OS via persistent sudoers entry (S:C).
Primary rating from Vendor (CSA).
CVSS VectorVendor: CSA
DescriptionCVE.org
Insufficient input validation in ABR allows a low-privileged user to inject malicious entries into the sudoers file, resulting in persistent root access that remained effective after the ABR session ended.
Executive ViewAI
Admin By Request (ABR) on macOS contains a persistent privilege escalation vulnerability (CVE-2026-78237, CVSS 7.8) that allows low-privileged users to inject malicious sudoers entries, granting permanent root access independent of session duration. Any macOS system running ABR is at risk of unauthorized administrative access that survives user logout, with no vendor patch currently available. Organizations must immediately assess ABR adoption across their macOS fleet and implement interim controls or alternative solutions.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) deploy sudoers file integrity monitoring to detect injection attempts, (2) restrict ABR administrative approvers to trusted administrators only, (3) implement audit logging for all privilege elevation sessions with off-system storage, (4) reduce ABR scope by disabling for service accounts and batch operations, (5) evaluate transition to native macOS authorization frameworks or third-party PAM solutions pending vendor patch availability.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
EUVD-2026-66332
GHSA-9v6j-cr5f-p2gx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB