Advisory record · GHSA-6hc9-cf8x-hf83

Quarkus OIDC can leak both ID and access tokens

CVSS 7.5 HighEPSS 0.0096 · 62nd percentile

Published by the GitHub Advisory Database at 4 Oct 2023, 12:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.quarkus:quarkus-oidcMaven<2.13.0.Final || >=3.0.0, <3.1.0.Final2.13.0.Final, 3.1.0.Final
Identifiers
GHSA-6hc9-cf8x-hf83 · CVE-2023-1584
Weakness (CWE)
CWE-200
Published
4 Oct 2023
Updated
3 May 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Quarkus OIDC (io.quarkus:quarkus-oidc, Maven) versions before 2.13.0.Final, and 3.0.0 up to but not including 3.1.0.Final, can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used. An attacker able to intercept that traffic could read sensitive user data from the ID token or use the access token to query user data from OIDC provider services. Upgrade to 2.13.0.Final or 3.1.0.Final.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0096, the 62nd percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:13 UTC First seen by agentprime
  2. 31 Oct 2026, 15:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.