Vulnerability in mercurius (CVE-2021-43801)
Summary
Vulnerability in mercurius (CVE-2021-43801). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 8.11.2 or later.
Original description
The description as published by the source.
Mercurius is a GraphQL adapter for Fastify. Any users from Mercurius@8.10.0 to 8.11.1 are subjected to a denial of service attack by sending a malformed JSON to /graphql unless they are using a custom error handler. The vulnerability has been fixed in https://github.com/mercurius-js/mercurius/pull/678 and shipped as v8.11.2. As a workaround users may use a custom error handler.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-43801 has been found in mercurius.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mercurius to 8.11.2 or later.
If unsure, ask your IT team or search "mercurius CVE-2021-43801" on the vendor's site.
CVE-2021-43801 (mercurius) — CWE-754
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 8.11.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-754) exists in mercurius.
Check the vendor advisory for the affected versions of mercurius.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 8.11.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mercurius' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mercurius' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mercuriusを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mercurius to 8.11.2ステージング環境で 8.11.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com