Mercurius: Incorrect Content-Type parsing can lead to CSRF attack

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

• CISA KEV Not listed.
• EPSS 0.0018, the 8th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 5 Mar 2026. New records show when each source confirmed them.

Sources

• GitHub Advisory Database: GHSA-v66j-6wwf-jc57
• OSV: GHSA-v66j-6wwf-jc57
• github.com/mercurius-js/mercurius/security/advisories/GHSA-v66j-6wwf-jc57
• nvd.nist.gov/vuln/detail/CVE-2025-64166
• github.com/mercurius-js/mercurius/pull/1187
• github.com/mercurius-js/mercurius/commit/962d402ec7a92342f4a1b7f5f04af01776838c3c
• github.com/mercurius-js/mercurius

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.