Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

CVE-2023-5720

HIGH

CVE-2023-5720 is a high-severity (CVSS 7.7) CWE-526 vulnerability in io.quarkus:quarkus-project. O3 Security confirms whether CVE-2023-5720 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus: build env information disclosure via gradle plugin

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

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-project3.0.0.CR1No fix

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. 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.

  2. Remediation status

    No patched version of io.quarkus:quarkus-project has shipped for CVE-2023-5720 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  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.

  4. How O3 protects you

    O3 pinpoints whether CVE-2023-5720 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 CVE-2023-5720. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects CVE-2023-5720 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

CVE-2023-5720: quarkus-project (High 7.7) | O3 Security