dbcve.org
Automotive Grade LinuxOperating system · Linuxfoundation

CVE-2026-37526

HIGH · 7.8 CVSS v3.1 Published 2026-05-01
Fix available
A fix is available. Upgrade to after 17.1.12 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AGL app-framework-binder (afb-daemon) through v19.90.0 contains a local privilege escalation vulnerability where the on_supervision_call function in src/afb-supervision.c dispatches all 8 supervision commands (Exit, Do, Sclose, Config, Trace, Debug, Token, slist) without any credential verification over an unprotected abstract Unix socket @urn:AGL:afs:supervision:socket. This allows any low-privileged local process to kill the daemon, execute arbitrary API calls, close user sessions, or leak global configuration.

MitigationImplement credential verification in the on_supervision_call function to authenticate clients before dispatching privileged commands, and add DAC protection to the abstract socket.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Automotive Grade LinuxOperating system
Affected:<= 17.1.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if afb-daemon is installed
    Check for the presence of the afb-daemon binary or app-framework-binder package using 'which afb-daemon' or 'dpkg -l | grep afb-daemon' or 'rpm -qa | grep afb'
    Affected if The package is installed and version is <= v19.90.0 or version cannot be determined but the daemon is present in AGL <= 17.1.12
  2. Determine afb-daemon version
    Run 'afb-daemon --version' or check the package version with your system package manager (dpkg/rpm)
    Affected if Version is v19.90.0 or earlier, or the --version flag is not available indicating an old build
  3. Verify the supervision socket is exposed
    Check for the abstract Unix socket using 'ss -x | grep urn:AGL:afs:supervision' or by examining /proc/net/unix for the socket name
    Affected if The socket @urn:AGL:afs:supervision:socket exists and is listening (indicates the vulnerable service is active)
  4. Check socket permissions and credential requirements
    Examine the source code or configuration for on_supervision_call in src/afb-supervision.c to verify if credential verification is implemented, or test by attempting to connect to the socket from a low-privileged process
    Affected if No credential or permission check is performed before dispatching supervision commands (Exit, Do, Sclose, Config, Trace, Debug, Token, slist)
  5. Confirm the system is Automotive Grade Linux
    Check the OS distribution using 'cat /etc/os-release' or 'cat /etc/agnt-version' on AGL systems
    Affected if Running Linuxfoundation Automotive Grade Linux version <= 17.1.12

You are affected if running AGL <= 17.1.12 with afb-daemon present and the supervision socket @urn:AGL:afs:supervision:socket is exposed without credential checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 17.1.12
Interim mitigation

Implement credential verification in the on_supervision_call function to authenticate clients before dispatching privileged commands, and add DAC protection to the abstract socket.

Fix this in Automotive Grade Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-37526 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-37526 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data