Answer in brief
CVE-2026-19625 records a Medium severity (CVSS 5.3) vulnerability in IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities. The current sources do not mark it as known exploited. The current feed maps IBM/Enterprise Build of Quarkus (generic), IBM/Enterprise Build of Quarkus (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps IBM/Enterprise Build of Quarkus (generic), IBM/Enterprise Build of Quarkus (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| IBM/Enterprise Build of Quarkusgeneric | 3.27.1 || 3.33.1 | Not reported |
| IBM/Enterprise Build of Quarkusgeneric | >=3.27.1 <=3.27.5 || >=3.33.1 <=3.33.3 | Not reported |
Published upstream
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 8, 2026
When a Quarkus application has multiple endpoints secured by individual OIDC provider tenants, such as "/oidc-provider1" that is secured by the OIDC Provider 1 and "/oidc-provider2" that is secured by the OIDC Provider 2, and an optional token introspection cache is also enabled, then a valid token issued by the OIDC Provider 1 that can be used to access "/oidc-provider1" can also be used to access "/oidc-provider2" that is secured by another OIDC Provider 2.
Quoted source text, attributed separately from HOL analysis.