# CVE-2026-37525: Privilege escalation in n/a

> Attackers can escalate privileges by exploiting a supervision command that nullifies credentials before executing arbitrary API calls.

- **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-2f7v-pjj3-rvvw

## What is CVE-2026-37525?

CVE-2026-37525 is a high-severity 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 contains a privilege escalation vulnerability in the supervision Do command. The on_supervision_call function in src/afb-supervision.c explicitly nullifies the request credentials by calling afb_context_change_cred(&xreq->context, NULL) before dispatching an attacker-controlled API call via xapi->itf->call(xapi->closure, xreq). The NULL propagation chain through afb-context.c:110 (context->credentials = afb_cred_addref(NULL)) and afb-cred.c:163 (returns NULL when cred is NULL) confirms that credentials are zeroed before the target API executes. The attacker controls both api and verb parameters via JSON input, allowing execution of any registered API with a NULL credential context. APIs that rely on context->credentials for authorization decisions may fail open when receiving NULL credentials, enabling privilege escalation. This vulnerability was introduced in commit abbb4599f0b921c6f434b6bd02bcfb277eecf745 on 2018-02-14.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Linuxfoundation Automotive Grade Linux.

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

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

## Is CVE-2026-37525 being exploited?

There is no known exploitation of CVE-2026-37525 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-37526](https://insights.sbomify.com/CVE-2026-37526/): Missing authorization 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-37525 and fix it if it is affected.

What it is: CVE-2026-37525 is a high-severity 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-37525 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-37525/ (Markdown: https://insights.sbomify.com/CVE-2026-37525/index.md)
```

## Sources

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

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