Skip to content
Web

CVE-2026-49473

8.8
High
EPSS 0.28%Patch availableAug 13, 2026

Authorization bypass in @cedar-policy Express middleware via query-string/path mismatch

common questions

Is CVE-2026-49473 being exploited?

Not confirmed. CVE-2026-49473 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-49473?

CVE-2026-49473 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-49473?

Yes. A fix has been recorded for CVE-2026-49473. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-49473 affect?

CVE-2026-49473 affects @cedar-policy/authorization-for-expressjs <0.3.0, Node.js Express applications using Cedar authorization middleware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-49473?

Upgrade to >=0.3.0; validate/sanitize request paths and use req.path for auth checks

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
@cedar-policy/authorization-for-expressjs <0.3.0Node.js Express applications using Cedar authorization middleware
impact

Authorization bypass: attacker appends query string to cause middleware to match a less-restrictive action and access restricted endpoints.

action required

Patch when possible

affected versions
cedar-policy authorization-for-expressjs
  • affected< 0.3.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free