CVE-2019-1020015: graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying J

Q: How do I fix CVE-2019-1020015?

graphql engine: upgrade to 1.0.0. Exact commands for each OS are on this page.

Q: Is CVE-2019-1020015 being exploited?

CVE-2019-1020015 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2019-1020015 affect?

CVE-2019-1020015 affects graphql engine. Severity is high (CVSS 7.5). graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.

Q: How urgent is CVE-2019-1020015?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2019-1020015 is a high-severity flaw (CVSS 7.5) affecting graphql engine. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.2% (top 32%)
CISA exploited list	No
Published	2019-07-29
Last modified	2026-06-17

Publisher (CNA): DWF · Vendor: hasura

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-07-29 13:15 UTCPublished CVE record published
2026-06-17 02:10 UTCUpdated Record last modified

hasura graphql engine UPGRADE

Affected: < 1.0.0 · 1.0.0 · 1.0.0 beta.1 · 1.0.0 beta.2

Fixed in: 1.0.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy graphql-engine || rpm -q graphql-engine || graphql-engine --version

2. UPGRADE to 1.0.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade graphql-engine

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade graphql-engine

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-1020015?

graphql engine: upgrade to 1.0.0. Exact commands for each OS are on this page.

Is CVE-2019-1020015 being exploited?

CVE-2019-1020015 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-1020015 affect?

CVE-2019-1020015 affects graphql engine. Severity is high (CVSS 7.5). graphql-engine (aka Hasura GraphQL Engine) before 1.0.0-beta.3 mishandles the audience check while verifying JWT.

How urgent is CVE-2019-1020015?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-54698 MEDIUM 5.9 UPGRADE Hasura is an open-source product that provides users GraphQL or REST APIs
CVE-2023-27588 HIGH 7.5 UPGRADE Hasura is an open-source product that provides users GraphQL or REST APIs
CVE-2022-46792 HIGH 8.8 UPGRADE Hasura GraphQL Engine before 2.15.2 mishandles row-level authorization in the Update Many API for Postgres bac
CVE-2021-47748 CRITICAL 9.8 DOWNGRADE Hasura GraphQL 1.3.3 contains a remote code execution vulnerability that allows attackers to execute arbitrary
CVE-2021-47715 MEDIUM 5.3 DOWNGRADE Hasura GraphQL 1.3.3 contains a server-side request forgery vulnerability that allows attackers to inject arbi

References

← Back to latest CVEs