Skip to content
Fencer Vulns
high 7.4

CVE-2026-19651 json

IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities

published 2026-09-08 2 mo ago modified 2026-09-09 2 mo ago also EUVD-2026-74180

cvss
7.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

IBM Enterprise Build of Quarkus 3.27.1 through 3.27.5, and 3.33.1 through 3.33.3 could allow an attacker to bypass authorization by manipulating URL query parameters due to incorrect mapping of values to untrusted query string input.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-19651 updated

quarkus-spring-web: quarkus-spring-web: Authorization bypass via URL query string manipulation

  • Red Hat build of Quarkus 3.27.5.SP1 quarkus-spring-web 3.27.5.redhat-00004
    fixed: vendor fix RHSA-2026:62515
  • Red Hat build of Quarkus 3.33.3.SP1 quarkus-spring-web 3.33.3.redhat-00005
    fixed: vendor fix RHSA-2026:62555
  • Red Hat build of Quarkus 3.27.5.SP1 jna 5.8.0, db2 1.21.4, h2 2.3.230, y18n 5.0.8, cliui 8.0.1, guice 5.1.0, +1009 more Red Hat build of Quarkus 3.33.3.SP1 jna 5.8.0, h2 2.4.240, y18n 5.0.8, cliui 8.0.1, guice 5.1.0, wasm 2.15.3, +1018 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2 mo ago

Exploit prediction

0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected products

  • IBM Enterprise Build of Quarkus

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.