dbcve.org
Graphql EngineApplication · Hasura

CVE-2021-47748

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hasura GraphQL 1.3.3 contains a remote code execution vulnerability that allows attackers to execute arbitrary shell commands through SQL query manipulation. Attackers can inject commands into the run_sql endpoint by crafting malicious GraphQL queries that execute system commands through PostgreSQL's COPY FROM PROGRAM functionality.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Hasura GraphQL Engine version 1.3.3 allows remote attackers to achieve arbitrary shell command execution by injecting commands through the run_sql endpoint. Attackers craft malicious GraphQL queries that leverage PostgreSQL's COPY FROM PROGRAM function to execute system commands on the host server.

MitigationUpgrade Hasura GraphQL Engine to a patched version beyond 1.3.3. Additionally, restrict access to the run_sql endpoint and disable the allow-list for SQL endpoints if not required in production environments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Graphql EngineApplication
Affected:= 1.3.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hasura GraphQL Engine version
    Check the version running in your environment by querying the GraphQL metadata endpoint or inspecting the container/process metadata
    Affected if the installed version is exactly 1.3.3 (other versions are not affected by this specific CVE)
  2. Verify run_sql endpoint is exposed
    Inspect your Hasura configuration and network exposure to determine if the run_sql endpoint is accessible (typically at /v2/query or /v1/query)
    Affected if the run_sql endpoint is exposed without proper access controls
  3. Check SQL endpoint allow-list status
    Review Hasura configuration for the SQL endpoint permissions - check if allow-list is disabled or if run_sql is explicitly permitted
    Affected if the allow-list is disabled or run_sql permission is granted, making exploitation possible

You are affected only if you are running exactly version 1.3.3 AND the run_sql endpoint is accessible without proper restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Hasura GraphQL Engine to a patched version beyond 1.3.3. Additionally, restrict access to the run_sql endpoint and disable the allow-list for SQL endpoints if not required in production environments.

Recommended fix Moderate confidence

Hasura GraphQL Engine version > 1.3.3 (e.g., 1.3.4 or later stable release)

  1. 1. Back up your current Hasura GraphQL Engine instance and database
  2. 2. Identify your current deployment method (Docker, Kubernetes, binary, or cloud service)
  3. 3. For Docker deployments: Update your image tag to a version newer than 1.3.3 (e.g., latest or a stable 1.x release post-1.3.3)
  4. 4. For other deployment methods: Obtain the updated binary or chart version from the official Hasura releases page at github.com/hasura/graphql-engine
  5. 5. Test the upgrade in a staging environment before production deployment
  6. 6. Deploy the upgraded version and verify GraphQL endpoint functionality
  7. 7. Monitor logs for any anomalies after upgrade
Caveat Minor version upgrades within 1.x typically maintain backward compatibility, but review release notes for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Graphql Engine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-47748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-47748 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data