@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.
CVE-2026-49473
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(medium)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 20%
- KEV
- Not listed
Published
June 30, 2026
Last Modified
August 13, 2026
Advisory Details (2)
Auto-updated Aug 12, 2026v0.3.0
Patch available: cedar-policy/authorization-for-expressjs v0.3.0
https://github.com/cedar-policy/authorization-for-expressjs/releases/tag/v0.3.0Authorization bypass in @cedar-policy/authorization-for-expressjs via query string manipulation · Advisory · cedar-policy/authorization-for-expressjs · GitHub
https://github.com/cedar-policy/authorization-for-expressjs/security/advisories/GHSA-g4w6-vmgf-xqvxVendor Advisories for CVE-2026-49473(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @cedar-policy/authorization-for-expressjs | — | 0.3.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 26× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 23:43 UTCEG score recompute
- 2026-08-24 11:39 UTCEG score recompute
- 2026-08-23 08:32 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 08:20 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 05:40 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 05:30 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 23:00 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:00 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 01:57 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:53 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:33 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 01:23 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 13:19 UTCEG score recompute
- 2026-08-13 00:22 UTCEG score recompute
Show 4 moreShow fewer
- 2026-07-30 10:26 UTCEG score recompute
- 2026-07-26 13:52 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-06-30 18:30 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-49473?
When was CVE-2026-49473 disclosed?
Is CVE-2026-49473 actively exploited?
What is the CVSS score of CVE-2026-49473?
How do I remediate CVE-2026-49473?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49473
Is Your Infrastructure Affected by CVE-2026-49473?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.