CVE-2026-49473
Full vulnerability record from the local CVENow database.
Description
@cedar-policy/authorization-for-expressjs is an open-source Express.js middleware that integrates Cedar authorization into Express applications by mapping HTTP requests to Cedar actions and evaluating authorization policies before allowing requests to proceed. Versions prior to 0.3.0 have an issue where, under certain circumstances, the middleware matches incoming requests against Cedar action mappings using req.originalUrl, which includes the query string, while Express routes requests using only the path component. The middleware uses req.originalUrl to match incoming requests against Cedar action mappings. In Express, req.originalUrl includes the query string, while route matching uses only the path. This creates a divergence between what Cedar authorizes and what Express executes. When an application defines separate actions for overlapping path prefixes with different authorization requirements (for example, GET /users for listing all users with admin-only access, and GET /users/{id} for retrieving a single user with any authenticated user access), an actor can append a query string to bypass the more restrictive policy. Sending GET /users/?x=1 causes the middleware to match against /users/{id} (with id parameter set to ?x=1) and evaluate the less restrictive action, while Express routes the request to the /users list handler. This allows inappropriate access to the more restrictive endpoint. This issue has been addressed in version 0.30. Some workarounds are available. Validate and sanitize incoming request paths before they reach the authorization middleware. Ensure that applications do not rely solely on the middleware for authorization when defining multiple actions on overlapping path prefixes with different permission levels.
View original CVE JSON
{
"id": "CVE-2026-49473",
"sourceIdentifier": "[email protected]",
"published": "2026-08-13T00:17:32.587",
"lastModified": "2026-10-24T16:10:00.153",
"vulnStatus": "Deferred",
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "@cedar-policy/authorization-for-expressjs is an open-source Express.js middleware that integrates Cedar authorization into Express applications by mapping HTTP requests to Cedar actions and evaluating authorization policies before allowing requests to proceed. Versions prior to 0.3.0 have an issue where, under certain circumstances, the middleware matches incoming requests against Cedar action mappings using req.originalUrl, which includes the query string, while Express routes requests using only the path component. The middleware uses req.originalUrl to match incoming requests against Cedar action mappings. In Express, req.originalUrl includes the query string, while route matching uses only the path. This creates a divergence between what Cedar authorizes and what Express executes. When an application defines separate actions for overlapping path prefixes with different authorization requirements (for example, GET /users for listing all users with admin-only access, and GET /users/{id} for retrieving a single user with any authenticated user access), an actor can append a query string to bypass the more restrictive policy. Sending GET /users/?x=1 causes the middleware to match against /users/{id} (with id parameter set to ?x=1) and evaluate the less restrictive action, while Express routes the request to the /users list handler. This allows inappropriate access to the more restrictive endpoint. This issue has been addressed in version 0.30. Some workarounds are available. Validate and sanitize incoming request paths before they reach the authorization middleware. Ensure that applications do not rely solely on the middleware for authorization when defining multiple actions on overlapping path prefixes with different permission levels."
},
{
"lang": "es",
"value": "@cedar-policy/authorization-for-expressjs es un middleware de Express.js de código abierto que integra la autorización de Cedar en aplicaciones Express mapeando solicitudes HTTP a acciones de Cedar y evaluando políticas de autorización antes de permitir que las solicitudes continúen. Las versiones anteriores a la 0.3.0 tienen un problema donde, bajo ciertas circunstancias, el middleware compara las solicitudes entrantes con las asignaciones de acciones de Cedar usando req.originalUrl, que incluye la cadena de consulta, mientras que Express enruta las solicitudes usando solo el componente de ruta. El middleware usa req.originalUrl para comparar las solicitudes entrantes con las asignaciones de acciones de Cedar. En Express, req.originalUrl incluye la cadena de consulta, mientras que la coincidencia de rutas usa solo la ruta. Esto crea una divergencia entre lo que Cedar autoriza y lo que Express ejecuta. Cuando una aplicación define acciones separadas para prefijos de ruta superpuestos con diferentes requisitos de autorización (por ejemplo, GET /users para listar todos los usuarios con acceso solo para administradores, y GET /users/{id} para recuperar un solo usuario con acceso para cualquier usuario autenticado), un actor puede añadir una cadena de consulta para eludir la política más restrictiva. Enviar GET /users/?x=1 hace que el middleware coincida con /users/{id} (con el parámetro id establecido en ?x=1) y evalúe la acción menos restrictiva, mientras que Express enruta la solicitud al gestor de la lista /users. Esto permite un acceso inapropiado al endpoint más restrictivo. Este problema ha sido abordado en la versión 0.30. Algunas soluciones provisionales están disponibles. Valide y sanee las rutas de solicitud entrantes antes de que lleguen al middleware de autorización. Asegúrese de que las aplicaciones no dependan únicamente del middleware para la autorización al definir múltiples acciones en prefijos de ruta superpuestos con diferentes niveles de permiso."
}
],
"affected": [
{
"source": "[email protected]",
"affectedData": [
{
"vendor": "cedar-policy",
"product": "authorization-for-expressjs",
"versions": [
{
"version": "< 0.3.0",
"status": "affected"
}
]
}
]
}
],
"metrics": {
"cvssMetricV31": [
{
"source": "[email protected]",
"type": "Secondary",
"cvssData": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"baseScore": 8.8,
"baseSeverity": "HIGH",
"attackVector": "NETWORK",
"attackComplexity": "LOW",
"privilegesRequired": "LOW",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"availabilityImpact": "HIGH"
},
"exploitabilityScore": 2.8,
"impactScore": 5.9
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"timestamp": "2026-08-13T13:10:02.673287Z",
"id": "CVE-2026-49473",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"version": "2.0.3"
}
}
]
},
"weaknesses": [
{
"source": "[email protected]",
"type": "Secondary",
"description": [
{
"lang": "en",
"value": "CWE-436"
},
{
"lang": "en",
"value": "CWE-863"
}
]
}
],
"references": [
{
"url": "https://github.com/cedar-policy/authorization-for-expressjs/releases/tag/v0.3.0",
"source": "[email protected]"
},
{
"url": "https://github.com/cedar-policy/authorization-for-expressjs/security/advisories/GHSA-g4w6-vmgf-xqvx",
"source": "[email protected]"
}
]
}