How severe is CVE-2026-40180?

No CVSS score has been assigned to CVE-2026-40180 yet. Review the advisory details and affected package list to assess your exposure.

How do I fix CVE-2026-40180?

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 CVE-2026-40180 is resolved across your whole dependency graph.

How do I detect CVE-2026-40180 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-40180 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-40180 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-40180 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 CVE-2026-40180?

CVE-2026-40180 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th 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 CVE-2026-40180?

CVE-2026-40180 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 CVE-2026-40180 published, and has it been updated?

CVE-2026-40180 was published on April 10, 2026 and was last updated on October 28, 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

CVE-2026-40180 — quarkus-openapi-generator

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

CVE-2026-40180 is a Path Traversal vulnerability in io.quarkiverse.openapi.generator:quarkus-openapi-generator. A fix is available for io.quarkiverse.openapi.generator:quarkus-openapi-generator — see the affected versions and patch details below.

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

Also known asGHSA-jx2w-vp7f-456q

Published

Apr 10, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40180.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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`io.quarkiverse.openapi.generator:quarkus-openapi-generator:2.16.0`

Affected Products

1 product · 2 configurations

Application

quarkus openapi generatorquarkiverse

< 2.15.0

1 version

2.15.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2026-40180 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 CVE-2026-40180 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works