# Hasura GraphQL Engine v2.45.8

- Product: Hasura GraphQL Engine (https://whatsnew.fyi/product/hasura)
- Vendor: Hasura
- Date: 2026-08-05
- Version: v2.45.8
- Original notes: https://github.com/hasura/graphql-engine/releases/tag/v2.45.8
- Permalink: https://whatsnew.fyi/product/hasura/releases/v2.45.8

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **security** — fix a bug in the mssql backend that could in certain cases allow an authenticated user to observe data they were not authorized for
- **changed** — event trigger names now undergo stricter validation, and must only contain alphanumeric, underscore and hyphen characters
- **changed** — improve the performance of order_by ...asc_nulls_first and ...desc_nulls_last in the MSSQL backend
- **security** — upgraded the Quarkus platform to remediate CVE-2026-50559 (authorization bypass in HTTP path-based policies via encoded characters)
- **security** — upgraded frontend/console npm dependencies to remediate HIGH/CRITICAL security advisories in axios, semver, and transitive packages
- **added** — add the HASURA_GRAPHQL_DISALLOW_INCONSISTENT_METADATA environment variable to enable --disallow-inconsistent-metadata for the metadata apply command in cli-migrations-v3
- **fixed** — fixed Postgres SSL connection failures for the self-hosted Ubuntu image when running on FIPS-enabled hosts

##### Changelog

This is a patch release for `v2.45`.

###### Bug fixes and improvements

###### Server

- **IMPORTANT**: fix a bug in the mssql backend that could in certain cases allow an authenticated user to observe data they were not authorized for. All MS SQL Server users are encouraged to upgrade. More details to be released.
- event trigger names now undergo stricter validation, and must only contain alphanumeric, underscore and hyphen characters. Formerly this was only a warning on `replace_metadata`. Server upgrades over metadata containing non-conforming names should continue to work, but names must be fixed before the next `replace_metadata`.
- Improve the performance of `order_by ...asc_nulls_first` and `...desc_nulls_last` in the MSSQL backend (contributed by Behzad Fattahi)

###### Data Connector

- super-connector: upgraded the Quarkus platform (3.33.1.1 -> 3.33.2.1, for `quarkus-vertx-http`) to remediate CVE-2026-50559 (HIGH: authorization bypass in HTTP path-based policies via encoded characters) flagged by the container image scan. _(Enterprise/cloud only)_

###### Build

- Upgraded frontend/console npm dependencies to remediate HIGH/CRITICAL security advisories (axios, semver, and transitive packages via Yarn resolutions). No user-facing behaviour change.
- cli-migrations-v3: add the `HASURA_GRAPHQL_DISALLOW_INCONSISTENT_METADATA` environment variable to the enable `--disallow-inconsistent-metadata` for the `metadata apply` command. 
- Fixed Postgres SSL connection failures for the self-hosted Ubuntu image when
running on FIPS-enabled hosts. Since v2.49.5 (Ubuntu Noble base), OpenSSL tried
to load a FIPS provider that is not shipped in the container, causing libpq SSL
context initialization to fail (could not create SSL context: could not load the shared library) and fall back to a rejected cleartext connection. The
image now sets `OPENSSL_FORCE_FIPS_MODE=0` (upstream-documented workaround for
Ubuntu bug LP#2141933) so it boots and negotiates TLS to Postgres on FIPS hosts.
This is a container bootability fix and is not a FIPS certification claim.