IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities (CVE-2026-19625) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-19625

IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities

Answer in brief

CVE-2026-19625 records a Unknown severity 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). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 8, 2026Updated Sep 8, 2026Source checked Sep 8, 2026First seen by HOL Sep 8, 2026Material review Sep 8, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Not reported

Why this deserves its current priority

A CVSS score is not reported in the current record. 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.

Affected scope and exposure questions

The current feed maps IBM/Enterprise Build of Quarkus (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
IBM/Enterprise Build of Quarkusgeneric	3.27.1 \|\| 3.33.1	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for IBM/Enterprise Build of Quarkus.
Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

Published upstream
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 8, 2026

Sources and claim methodology

Source referenceibm.com

Upstream source description

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.