Skip to content

← Public intelligence

Maven package

io.quarkiverse.openapi.generator:quarkus-openapi-generator

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.3MavenPublished

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

    CVE-2026-42333 · GHSA-fr8f-rwjx-f32v

    Affected
    • Maven io.quarkiverse.openapi.generator:quarkus-openapi-generator < 2.16.0-lts; >= 2.16.0, <= 2.16.0
    Fixed in
    2.17.02.16.0-lts· Vendor fix available
    Issue
    The generated authentication filter matches OpenAPI path templates too broadly when deciding whether to attach credentials. A security scheme configured for one operation can therefore be applied to a different same-method operation whose path only partially resembles the protected template, causing bearer tokens, API keys, or basic credentials to be sent to unintended endpoints. Details The runtime authentication layer selects credentials by comparing the outgoing request path and method against the set of protected OpenAPI operations. Path-template matching treats {param} placeholders as ., which incorrectly allows a single path parameter to consume /. As a result, a protected path such as /repos/{ref} also matches /repos/foo/bar, even though /repos/{owner}/{repo} is a different operation. When a client invokes the unprotected operation, the authentication filter still concludes that the protected operation matched and attaches its credentials. This affects authentication…

    Recommended action: Upgrade to 2.17.0 or 2.16.0-lts (pre-release) by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 6.3MavenPublished

    quarkus-openapi-generator extension has Zip Slip Path Traversal in ApicurioCodegenWrapper class

    CVE-2026-40180 · GHSA-jx2w-vp7f-456q

    Affected
    • Maven io.quarkiverse.openapi.generator:quarkus-openapi-generator <= 2.15.0
    Fixed in
    2.16.0· Vendor fix available
    Issue
    A path traversal vulnerability was discovered in the quarkus-openapi-generator extension Details The unzip() method in ApicurioCodegenWrapper.java extracts ZIP entries without validating that the resolved file path stays within the intended output directory. At line 101, the destination is constructed as new File(toOutputDir, entry.getName()) and the content is written immediately. A malicious ZIP archive containing entries with path traversal sequences (e.g., ../../malicious.java) would write files outside the target directory. The interesting thing is that the client module in the same repository already has the correct fix. OpenApiGeneratorStreamCodeGen.java at line 137 performs proper normalize() and startsWith() validation. The server module was simply missed. PoC This vulnerability is exploitable when an attacker controls or can intercept the ZIP archive served by the Apicurio registry. In environments where the registry connection is over an untrusted network or where…

    Recommended action: Upgrade to 2.16.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →