Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1amended

EasyAdmin custom-action dispatcher bypasses access_control on other routes

CVE-2026-81892GHSA-g2fm-8hr4-j82h

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (easycorp/easyadmin-bundle 5.5.1, 4.29.16), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
  • CVE-2026-81892: 0.45% estimated exploitation activity in the next 30 days; percentile 38.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary EasyAdmin serves all backend requests through a single dashboard route and, for custom actions (Action::linkToRoute() / MenuItem::linkToRoute()), swaps the executed controller based on the routeName query parameter on the kernel.controller event. That swap happens after Symfony's security firewall has already evaluated accesscontrol against the original dashboard URL, and the routeName value was not validated. As a result, a path-based accesscontrol rule protecting the target route was never evaluated, so a low-privilege backend user could reach a more restricted route by name. Impact Any application where accesscontrol (or another path-based Symfony security rule) protects some routes more strictly than the dashboard URL used to reach EasyAdmin. An attacker 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-g2fm-8hr4-j82h

  2. Revision 1 · created ·

    Published from osv record GHSA-g2fm-8hr4-j82h

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-81892

Advisory: EasyAdmin custom-action dispatcher bypasses access_control on other routes
IDs: CVE-2026-81892, GHSA-g2fm-8hr4-j82h
Record: https://patchnext.com/advisories/cve-2026-81892 (revision 2, source checked 26 Oct 2026, 14:53 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: easycorp/easyadmin-bundle 5.5.1, 4.29.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist easycorp/easyadmin-bundle: affected >= 4.0.0, < 4.29.16; >= 5.0.0, < 5.5.1; fixed in 5.5.1, 4.29.16

## Suggested inspection (read-only)
- Packagist easycorp/easyadmin-bundle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on easycorp/easyadmin-bundle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-g2fm-8hr4-j82h (OSV record GHSA-g2fm-8hr4-j82h lists affected ranges: Packagist easycorp/easyadmin-bundle >=4.0.0 =5.0.0 <5.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-g2fm-8hr4-j82h (GitHub-reviewed advisory GHSA-g2fm-8hr4-j82h lists affected ranges: Packagist easycorp/easyadmin-bundle >=4.0.0 =5.0.0 <5.5.1)

Commands are suggestions: review each one before running it.

Loading voting…