CVE-2026-37526
HighWhat is CVE-2026-37526?
AGL app-framework-binder (afb-daemon) through v19.90.0 allows any local process to execute privileged supervision commands (Exit, Do, Sclose, Config, Trace, Debug, Token, slist) without authentication via the abstract Unix socket @urn:AGL:afs:supervision:socket. The on_supervision_call function in src/afb-supervision.c dispatches all 8 commands without any credential verification. The abstract socket has no DAC protection, as acknowledged in the official CAUTION comment in src/afs-supervision.h. This allows a low-privileged local process to kill the daemon (DoS via Exit command), execute arbitrary API calls (via Do command), close arbitrary user sessions (via Sclose command), or leak the entire global configuration (via Config command). The vulnerability was introduced in commit b8c9d5de384efcfa53ebdb3f0053d7b3723777e1 on 2017-06-29.
CVSS Vector Breakdown
CVSS 3.1Requires local access — attacker must be logged in or have physical access to the device.
No special conditions required. Exploit can be performed reliably and repeatedly.
Basic user account required (e.g. standard login without admin rights).
No user interaction required. Exploit runs without any victim action.
Exploiting the vulnerability only affects the vulnerable component itself.
Complete loss of confidentiality. All data on the component may be exposed.
Complete loss of integrity. Attacker can modify any file or data on the component.
Complete denial of service. The component becomes fully unavailable.
FAQ
CVE-2026-37526 has a CVSS score of 7.8/10, rated as High. This is a high severity vulnerability and should be patched as soon as possible.
CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-37526 scores 7.8/10 (High). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.
The list of devices confirmed to be affected by CVE-2026-37526 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.
Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.