CVE-2026-19625: 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…

PriorityP429medium5.3CVSS 3.1

AVNACLPRNUINSUCLINAN

EPSS

0.23%

12.7th percentile

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.

Affected

3 ranges

Vendor	Product	Version range	Fixed in
exploit-intelligence-tech-preview	agent-client-rhel9	—	—
ibm	enterprise_build_of_quarkus	3.27.1 – 3.27.5	—
ibm	enterprise_build_of_quarkus	3.33.1 – 3.33.3	—

CVSS provenance

nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

vendor_redhat8.7HIGH

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.