# CVE-2026-19625: IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities

> Attackers can access endpoints secured by different OIDC providers using tokens from another provider when token introspection caching is enabled.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 10 Sep 2026

## What is CVE-2026-19625?

CVE-2026-19625 is a medium-severity authentication bypass vulnerability in IBM Enterprise Build of Quarkus, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-19625?


## How do I fix CVE-2026-19625?

No fix has been published for CVE-2026-19625 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19625 being exploited?

There is no known exploitation of CVE-2026-19625 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19625 and fix it if it is affected.

What it is: CVE-2026-19625 is a medium-severity authentication bypass vulnerability in IBM Enterprise Build of Quarkus, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19625 in the wild and no public exploit code.

Affected product: IBM Enterprise Build of Quarkus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19625/ (Markdown: https://insights.sbomify.com/CVE-2026-19625/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19625
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19625
- OSV: https://osv.dev/vulnerability/CVE-2026-19625

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19625/
Summaries are generated and may contain mistakes; the official description above is the record.