NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2023-5720 — quarkus-project

HIGH

CVE-2023-5720 is a high-severity (CVSS 7.7) CWE-526 vulnerability in io.quarkus:quarkus-project. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Quarkus: build env information disclosure via gradle plugin

Also known asGHSA-p62q-5483-h57v
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk+0.14%
Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk
0.25%1.26%2.27%3.28%2.7%1.0%May 26Sep 26Nov 26

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

1 pkg affected
☕io.quarkus:quarkus-project

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, where it does not properly sanitize artifacts created using the Gradle plugin, allowing certain build system information to remain. This flaw allows an attacker to access potentially sensitive information from the build system within the application.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
☕Mavenio.quarkus:quarkus-project≥ 3.0.0.CR1No fix

Affected Products

1 product · 3 configurations
Application
quarkusquarkus
≥ 3.0.1 && < 3.2.8
1 version
3.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Remediation status

    The records we use list no patched version of io.quarkus:quarkus-project for CVE-2023-5720. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    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.

Frequently Asked Questions

A flaw was found in Quarkus, where it does not properly sanitize artifacts created using the Gradle plugin, allowing certain build system information to remain. This flaw allows an attacker to access potentially sensitive information from the build system within the application.
O3 Security · Impact-Aware SCA

Is CVE-2023-5720 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2023-5720: quarkus-project (High 7.7)