# CVE-2026-81892: EasyAdmin custom-action dispatcher bypasses access_control on other routes

> Low-privilege users can bypass path-based access controls to execute arbitrary backend routes by manipulating the routeName parameter in EasyAdmin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 31 Aug 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-g2fm-8hr4-j82h

## What is CVE-2026-81892?

CVE-2026-81892 is a high-severity missing authorization vulnerability in EasyCorp EasyAdminBundle, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

EasyAdmin is a fast and modern admin generator for Symfony applications. From 4.0.0 until 4.29.16 and 5.5.1, EasyAdmin serves all backend requests through a single dashboard route and, for custom actions (Action::linkToRoute() and MenuItem::linkToRoute()), swaps the executed controller based on the routeName query parameter on the kernel.controller event. The swap happens after Symfony's security firewall has already evaluated access_control against the original dashboard URL, and the routeName value was not validated. As a result, a path-based access_control rule protecting the target route was never evaluated, so a low-privilege backend user who can reach a single EasyAdmin URL and knows a target route's name can execute that route's controller, bypassing the path-based rule. Only path-based protections are bypassed. Routes whose controller enforces its own authorization with #[IsGranted] or denyAccessUnlessGranted() remain protected because those checks are recomputed against the swapped-in controller. This issue is fixed in versions 4.29.16 and 5.5.1.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

4 open source packages ship an affected version, including easycorp/easyadmin-bundle.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `easycorp/easyadmin-bundle` | Packagist | From 4.0.0 | 4.29.16 |
| `easycorp/easyadmin-bundle` | Packagist | From 4.0.0 | 4.29.16 |
| `easycorp/easyadmin-bundle` | Packagist | From 5.0.0 | 5.5.1 |
| `easycorp/easyadmin-bundle` | Packagist | From 5.0.0 | 5.5.1 |

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

Upgrade easycorp/easyadmin-bundle to a fixed version for your release line: 4.29.16 or 5.5.1.

## Is CVE-2026-81892 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81892 is a high-severity missing authorization vulnerability in EasyCorp EasyAdminBundle, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-81892 in the wild and no public exploit code.

Affected packages and fixed versions:
- easycorp/easyadmin-bundle (Packagist): affected from 4.0.0; fixed in 4.29.16
- easycorp/easyadmin-bundle (Packagist): affected from 4.0.0; fixed in 4.29.16
- easycorp/easyadmin-bundle (Packagist): affected from 5.0.0; fixed in 5.5.1
- easycorp/easyadmin-bundle (Packagist): affected from 5.0.0; fixed in 5.5.1

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-81892/ (Markdown: https://insights.sbomify.com/CVE-2026-81892/index.md)
```

## Sources

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

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