How severe is GHSA-6hc9-cf8x-hf83?

GHSA-6hc9-cf8x-hf83 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6hc9-cf8x-hf83?

GHSA-6hc9-cf8x-hf83 affects the following packages: io.quarkus:quarkus-oidc (Maven), io.quarkus:quarkus-oidc (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6hc9-cf8x-hf83?

Update io.quarkus:quarkus-oidc to 2.13.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hc9-cf8x-hf83 is resolved across your whole dependency graph.

How do I detect GHSA-6hc9-cf8x-hf83 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-oidc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6hc9-cf8x-hf83 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-6hc9-cf8x-hf83 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6hc9-cf8x-hf83 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6hc9-cf8x-hf83?

GHSA-6hc9-cf8x-hf83 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6hc9-cf8x-hf83?

GHSA-6hc9-cf8x-hf83 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6hc9-cf8x-hf83 published, and has it been updated?

GHSA-6hc9-cf8x-hf83 was published on October 4, 2023 and was last updated on May 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

Quarkus OIDC can leak both ID and access tokensGHSA-6hc9-cf8x-hf83

HIGHFix: quarkusio/quarkus#32192

GHSA-6hc9-cf8x-hf83 is a high-severity (CVSS 7.5) Information Exposure vulnerability in io.quarkus:quarkus-oidc. A fix is available for io.quarkus:quarkus-oidc — see the affected versions and patch details below.

Also known asCVE-2023-1584

Published

Oct 4, 2023

Updated

May 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕io.quarkus:quarkus-oidc☕io.quarkus:quarkus-oidc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.quarkus:quarkus-oidc`	all versions	2.13.0.Final`io.quarkus:quarkus-oidc:2.13.0.Final`
☕Maven	`io.quarkus:quarkus-oidc`	≥ 3.0.0&&< 3.1.0.Final	3.1.0.Final`io.quarkus:quarkus-oidc:3.1.0.Final`

Affected Products

1 product · 1 configurations

Application

quarkusquarkus

< 2.13.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-oidc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-oidc to 2.13.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hc9-cf8x-hf83 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Red Hat Build of Quarkus flaw happens because the cookie contains a token that token could potentially be more useful to attackers than a normal session cookie hijacking attack. Other potentially higher security applications may accept the same token from the cookie, while with a normal session hijacking attack it is…

Product	Fixed in	Advisory
Red Hat build of Quarkus 2.13.8.Final	`io.quarkus/quarkus-oidc:2.13.8.Final-redhat-00004`	RHSA-2023:3809
RHINT Service Registry 2.5.4 GA	`quarkus-oidc`	RHSA-2023:7653

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6hc9-cf8x-hf83 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works