# CVE-2026-37526: Missing authorization in n/a

> Local attackers can execute privileged commands and leak configuration via an unauthenticated Unix socket in the AGL app-framework-binder daemon.

- **Severity:** High 7.8 (`CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-6c74-7qpx-6vqc

## What is CVE-2026-37526?

CVE-2026-37526 is a high-severity missing authorization vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-37526?

It affects 1 product.


Products: Linuxfoundation Automotive Grade Linux.

## How do I fix CVE-2026-37526?

No fix has been published for CVE-2026-37526 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-37526 being exploited?

There is no known exploitation of CVE-2026-37526 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-37531](https://insights.sbomify.com/CVE-2026-37531/): Path traversal in n/a (critical 9.8)
- [CVE-2026-37525](https://insights.sbomify.com/CVE-2026-37525/): Privilege escalation in n/a (high 7.8)
- [CVE-2026-37530](https://insights.sbomify.com/CVE-2026-37530/): Memory corruption in n/a (high 7.5)
- [CVE-2026-37532](https://insights.sbomify.com/CVE-2026-37532/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-37526 and fix it if it is affected.

What it is: CVE-2026-37526 is a high-severity missing authorization vulnerability in n/a, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-37526 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-37526/ (Markdown: https://insights.sbomify.com/CVE-2026-37526/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-37526
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-37526
- OSV: https://osv.dev/vulnerability/CVE-2026-37526

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-37526/
Summaries are generated and may contain mistakes; the official description above is the record.