CVE-2026-49473
Received Received - Intake

Authorization Bypass in Cedar Policy for Express.js

Vulnerability report for CVE-2026-49473, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
cedar-policy authorization-for-expressjs to 0.3.0 (exc)
cedar-policy authorization-for-expressjs 0.3.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CWE-436 Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an authorization bypass in the @cedar-policy/authorization-for-expressjs package affecting versions 0.2.0 and earlier. The middleware uses req.originalUrl (including query strings) to match requests against Cedar authorization policies, while Express routes requests based only on the path. This mismatch allows attackers to append query strings to bypass more restrictive policies. For example, a request like GET /users/?x=1 is interpreted as GET /users/{id} by the middleware but routed to /users by Express, granting unauthorized access.

Detection Guidance

Check if your system uses @cedar-policy/authorization-for-expressjs version 0.2.0 or earlier by inspecting package.json or running npm list @cedar-policy/authorization-for-expressjs. Monitor logs for requests to endpoints with overlapping path prefixes where query strings may alter authorization outcomes.

Impact Analysis

This vulnerability allows attackers to bypass authorization policies, potentially gaining unauthorized access to sensitive endpoints or data. It could lead to data breaches, privilege escalation, or unauthorized actions being performed. The impact includes confidentiality, integrity, and availability risks, with a CVSS score of 8.8 indicating high severity.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements under GDPR (data protection) and HIPAA (health information privacy). Organizations using this middleware may face regulatory penalties, legal liabilities, and reputational damage due to non-compliance with data protection standards.

Mitigation Strategies

Upgrade to version 0.3.0 or later immediately. If upgrading is not possible, validate and sanitize incoming request paths before they reach the authorization middleware to remove query strings. Avoid relying solely on the middleware for authorization when overlapping path prefixes have different permission levels.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-49473. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart