# GHSA-9m6v-8fxc-4r44: Sulu: Used API Keys may be available via Admin API

> Logged-in users with specific permissions can view project API keys via the admin API if the field is exposed, leading to information disclosure.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 May 2026

## What is GHSA-9m6v-8fxc-4r44?

GHSA-9m6v-8fxc-4r44 is a vulnerability in sulu/sulu, published on 18 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Impact

The users endpoint controller exposes a project's apiKey field to the logged-in user, provided they have permission for that endpoint. This only has impact if a project itself uses that specific field, Sulu itself does nothing with it and has no authentication per apiKey in its core.

### Patches

A patch is released with Version 2.6.23 and 3.0.5.

### Workarounds

Remove the field descriptor by patch the UserController.php File in Sulu Security Bundle.

## Which versions are affected by GHSA-9m6v-8fxc-4r44?

4 open source packages ship an affected version, including sulu/sulu.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sulu/sulu` | Packagist | All versions | 2.6.23 |
| `sulu/sulu` | Packagist | All versions | 2.6.23 |
| `sulu/sulu` | Packagist | From 3.0.0-alpha1 | 3.0.6 |
| `sulu/sulu` | Packagist | From 3.0.0-alpha1 | 3.0.6 |

## How do I fix GHSA-9m6v-8fxc-4r44?

Upgrade sulu/sulu to a fixed version for your release line: 2.6.23 or 3.0.6.

## Is GHSA-9m6v-8fxc-4r44 being exploited?

There is no known exploitation of GHSA-9m6v-8fxc-4r44 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-9m6v-8fxc-4r44 and fix it if it is affected.

What it is: GHSA-9m6v-8fxc-4r44 is a vulnerability in sulu/sulu, published on 18 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-9m6v-8fxc-4r44 in the wild and no public exploit code.

Affected packages and fixed versions:
- sulu/sulu (Packagist): affected all versions; fixed in 2.6.23
- sulu/sulu (Packagist): affected all versions; fixed in 2.6.23
- sulu/sulu (Packagist): affected from 3.0.0-alpha1; fixed in 3.0.6
- sulu/sulu (Packagist): affected from 3.0.0-alpha1; fixed in 3.0.6

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/GHSA-9m6v-8fxc-4r44/ (Markdown: https://insights.sbomify.com/GHSA-9m6v-8fxc-4r44/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-9m6v-8fxc-4r44

---
From sbomify Insights: https://insights.sbomify.com/GHSA-9m6v-8fxc-4r44/
Summaries are generated and may contain mistakes; the official description above is the record.