CVE-2026-33504 | ory hydra up to 26.1.x Admin API sql injection

VDB-353702 · CVE-2026-33504 · GCVE-0-2026-33504 ORY HYDRA UP TO 26.1.X ADMIN API SQL INJECTION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 5.8 $0-$5k 2.89+ Summaryinfo A vulnerability was found in ory hydra up to 26.1.x. It has been declared as critical. This affects an unknown function of the component Admin API. Such manipulation leads to sql injection. This vulnerability is uniquely identified as CVE-2026-33504. The attack can be launched remotely. No exploit exists. It is recommended to upgrade the affected component. Detailsinfo A vulnerability, which was classified as critical, has been found in ory hydra up to 26.1.x. Affected by this issue is some unknown processing of the component Admin API. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes: Ory Hydra is an OAuth 2.0 Server and OpenID Connect Provider. Prior to version 26.2.0, the listOAuth2Clients, listOAuth2ConsentSessions, and listTrustedOAuth2JwtGrantIssuers Admin APIs in Ory Hydra are vulnerable to SQL injection due to flaws in its pagination implementation. Pagination tokens are encrypted using the secret configured in `secrets.pagination`. If this value is not set, Hydra falls back to using `secrets.system`. An attacker who knows this secret can craft their own tokens, including malicious tokens that lead to SQL injection. This issue can be exploited when one or more admin APIs listed above are directly or indirectly accessible to the attacker; the attacker can pass a raw pagination token to the affected API; and the configuration value `secrets.pagination` is set and known to the attacker, or `secrets.pagination` is not set and `secrets.system` is known to the attacker. An attacker can execute arbitrary SQL queries through forged pagination tokens. As a first line of defense, immediately configure a custom value for `secrets.pagination` by generating a cryptographically secure random secret. Next, upgrade Hydra to the fixed version, 26.2.0 as soon as possible. The advisory is available at github.com. This vulnerability is handled as CVE-2026-33504 since 03/20/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1505 by the MITRE ATT&CK project. Upgrading to version 26.2.0 eliminates this vulnerability. Productinfo Vendor ory Name hydra Version 26.0 26.1 Website Product: https://github.com/ory/hydra/ CPE 2.3info 🔒 🔒 CPE 2.2info 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 5.9 VulDB Meta Temp Score: 5.8 VulDB Base Score: 4.7 VulDB Temp Score: 4.5 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.2 CNA Vector (GitHub_M): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Sql injection CWE: CWE-89 / CWE-74 / CWE-707 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: Upgrade Status: 🔍 0-Day Time: 🔒 Upgrade: hydra 26.2.0 Timelineinfo 03/20/2026 CVE reserved 03/26/2026 +6 days Advisory disclosed 03/26/2026 +0 days VulDB entry created 03/26/2026 +0 days VulDB entry last update Sourcesinfo Product: github.com Advisory: github.com Status: Confirmed CVE: CVE-2026-33504 (🔒) GCVE (CVE): GCVE-0-2026-33504 GCVE (VulDB): GCVE-100-353702 Entryinfo Created: 03/26/2026 19:07 Changes: 03/26/2026 19:07 (64) Complete: 🔍 Cache ID: 99:35B:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸