CVE-2026-49473

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

@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 v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 computed
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

Published

June 30, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_release.
github_release Patch Available

v0.3.0

Patch available: cedar-policy/authorization-for-expressjs v0.3.0

https://github.com/cedar-policy/authorization-for-expressjs/releases/tag/v0.3.0
githubMentions a patch (unverified)

Authorization 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-xqvx

Vendor 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)
PackageVulnerable rangeFix by version rangeDependents
@cedar-policy/authorization-for-expressjs—
  • every version up to 0.3.0: fixed in 0.3.0
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× 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.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-28 13:51 UTCEPSS rescore
  11. 2026-09-27 13:48 UTCEPSS rescore
  12. 2026-09-26 15:59 UTCEPSS rescore
  13. 2026-09-26 00:27 UTCEPSS rescore
  14. 2026-09-23 17:53 UTCEPSS rescore
  15. 2026-09-23 07:19 UTCEG score recompute
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 06:48 UTCEG score recompute
  19. 2026-09-16 14:08 UTCEPSS rescore
  20. 2026-09-16 05:15 UTCEPSS rescore
  21. 2026-09-14 00:47 UTCEG score recompute
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-12 15:09 UTCEG score recompute
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-10 09:35 UTCEPSS rescore
Show 45 more
  1. 2026-09-09 22:59 UTCEG score recompute
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-07 16:01 UTCEPSS rescore
  4. 2026-09-06 14:35 UTCEG score recompute
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 14:12 UTCEPSS rescore
  8. 2026-09-01 13:54 UTCEPSS rescore
  9. 2026-09-01 04:40 UTCEPSS rescore
  10. 2026-08-30 19:17 UTCEPSS rescore
  11. 2026-08-30 18:02 UTCEG score recompute
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 22:41 UTCEG score recompute
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 23:43 UTCEG score recompute
  19. 2026-08-24 11:39 UTCEG score recompute
  20. 2026-08-23 08:32 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-22 08:20 UTCEG score recompute
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-21 05:40 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-20 05:30 UTCEG score recompute
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 23:00 UTCEG score recompute
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-17 14:00 UTCEG score recompute
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-17 01:57 UTCEG score recompute
  33. 2026-08-16 14:56 UTCEPSS rescore
  34. 2026-08-16 13:53 UTCEG score recompute
  35. 2026-08-16 02:14 UTCEPSS rescore
  36. 2026-08-15 01:33 UTCEG score recompute
  37. 2026-08-15 01:30 UTCEPSS rescore
  38. 2026-08-14 01:23 UTCEG score recompute
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 13:19 UTCEG score recompute
  41. 2026-08-13 00:22 UTCEG score recompute
  42. 2026-07-30 10:26 UTCEG score recompute
  43. 2026-07-26 13:52 UTCEG score recompute
  44. 2026-07-23 03:18 UTCEG score recompute
  45. 2026-06-30 18:30 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-49473?
CVE-2026-49473 is a high vulnerability published on June 30, 2026. @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…
When was CVE-2026-49473 disclosed?
CVE-2026-49473 was first published on June 30, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49473 actively exploited?
CVE-2026-49473 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49473?
CVE-2026-49473 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49473?
A fix for CVE-2026-49473 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49473 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49473

Explore →

Is Your Infrastructure Affected by CVE-2026-49473?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.