Skip to content
VulniPulse
Advisory severityHigh8.6Red Hat Linux

High [CVE-2026-77874] SQL Injection via unescaped JSON path segment allows data exfiltration and authorization bypass

This high-severity Red Hat Linux advisory covers CVE-2026-77874; related products: Cryostat 4, Red Hat build of Debezium 3, Red Hat Build of Keycloak.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-77874 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

SQL Injection via unescaped JSON path segment allows data exfiltration and authorization bypass. Red Hat rates this important (CVSS 8.6).

Weakness: CWE-89.

Affected products named by the advisory: Cryostat 4; Red Hat build of Debezium 3; Red Hat Build of Keycloak; Red Hat JBoss Enterprise Application Platform 7; and 4 more.

Affected products named by the advisory: Red Hat OpenShift AI (RHOAI); Red Hat OpenStack Platform 13 (Queens); Red Hat Satellite 6; Red Hat Single Sign-On 7.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this vulnerability, applications using Hibernate ORM should avoid passing untrusted user-controlled input directly as JSON path arguments to `json_query`, `json_exists`, or `json_value` functions. If dynamic JSON querying is necessary, strictly validate or whitelist the JSON path input against a predefined pattern (e.g., allowing only alphanumeric characters and dots) before use.

Official advisory · high-confidence parse· fetched 12 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.