Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-fr8f-rwjx-f32v

quarkus-openapi-generator has overly broad path-parameter matching that sends authentication headers to unintended operations

CVSS 6.3 MediumEPSS 0.0040 · 34th percentile

Published by the GitHub Advisory Database at 4 May 2026, 21:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.quarkiverse.openapi.generator:quarkus-openapi-generatorMaven<2.16.0-lts || >=2.16.0, <2.17.02.16.0-lts, 2.17.0
Identifiers
GHSA-fr8f-rwjx-f32v · CVE-2026-42333
Weakness (CWE)
CWE-200
Tags
Published
4 May 2026
Updated
13 May 2026

Machine-written summary

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

The quarkus-openapi-generator package, versions before 2.16.0-lts and from 2.16.0 up to 2.17.0, has overly broad path-template matching in its generated authentication filter. A client request whose path only partly resembles a protected operation can receive that operation's credentials, so bearer tokens, API keys, or basic credentials may be sent to unintended endpoints by ordinary generated-client use, with no special access needed. Upgrade to 2.16.0-lts or 2.17.0.

Written 3 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
6.3 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0040, the 34th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 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.