How severe is GHSA-jx2w-vp7f-456q?

No CVSS score has been assigned to GHSA-jx2w-vp7f-456q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jx2w-vp7f-456q?

GHSA-jx2w-vp7f-456q affects the following packages: io.quarkiverse.openapi.generator:quarkus-openapi-generator (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jx2w-vp7f-456q?

Update io.quarkiverse.openapi.generator:quarkus-openapi-generator to 2.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jx2w-vp7f-456q is resolved across your whole dependency graph.

How do I detect GHSA-jx2w-vp7f-456q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkiverse.openapi.generator:quarkus-openapi-generator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jx2w-vp7f-456q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-jx2w-vp7f-456q?

O3 pinpoints whether GHSA-jx2w-vp7f-456q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jx2w-vp7f-456q actively exploited in the wild?

No public exploit code has been indexed for GHSA-jx2w-vp7f-456q 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 type of vulnerability is GHSA-jx2w-vp7f-456q?

GHSA-jx2w-vp7f-456q is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-jx2w-vp7f-456q published, and has it been updated?

GHSA-jx2w-vp7f-456q was published on April 8, 2026 and was last updated on April 10, 2026. 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

GHSA-jx2w-vp7f-456q

Fix: quarkiverse/quarkus-openapi-generator@08b4064

GHSA-jx2w-vp7f-456q is a Path Traversal vulnerability in io.quarkiverse.openapi.generator:quarkus-openapi-generator. O3 Security confirms whether GHSA-jx2w-vp7f-456q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-40180

Published

Apr 8, 2026

Updated

Apr 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

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

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

Summary

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 TLS is not properly configured, exploitation becomes practical. The attack occurs at build/codegen time.

Create a ZIP file containing an entry named ../../proof.txt with arbitrary content
Configure quarkus-openapi-generator to use the server (Apicurio) code generation path
Serve the malicious ZIP from a controlled or MITM'd Apicurio registry endpoint
Trigger code generation
Observe that proof.txt is written two directories above the intended output

Impact

An attacker who can serve a crafted ZIP to the code generation pipeline could write arbitrary files on the build machine. This could overwrite source files, inject malicious code into the build output, or modify configuration files. In CI/CD environments, this could lead to supply chain compromise.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.quarkiverse.openapi.generator:quarkus-openapi-generator`	all versions	2.16.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkiverse.openapi.generator:quarkus-openapi-generator. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.quarkiverse.openapi.generator:quarkus-openapi-generator to 2.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jx2w-vp7f-456q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jx2w-vp7f-456q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jx2w-vp7f-456q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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 clien

O3 Security · Impact-Aware SCA

Is GHSA-jx2w-vp7f-456q in your dependencies?

O3 detects GHSA-jx2w-vp7f-456q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works