CVE-2023-5720 | Quarkus: build env information disclosure via gradle plugin

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.

Published: 2023-11-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-5720 is rated Moderate Risk (46.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.81%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-5720

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 3.00% 0.81% -2.18%
2 2026-06-08 2.71% 3.00% +0.29%
3 2026-04-26 — 2.71% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-5720

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.1 4.0 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-5720

GitHub Security Advisory for CVE-2023-5720

GHSA-p62q-5483-h57v · Severity: high · Ecosystem: maven — Quarkus does not properly sanitize artifacts created from its use of the Gradle plugin, allowing certain build system information to remain

OS Trackers for CVE-2023-5720

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2023-5720

Affected software / configurations for CVE-2023-5720

Vendor Product Version Raw CPE
quarkus quarkus >= 3.0.1, < 3.2.8 cpe:2.3:a:quarkus:quarkus:*:*:*:*:*:*:*:*
quarkus quarkus 3.0.0 cpe:2.3:a:quarkus:quarkus:3.0.0:candidate_release1:*:*:*:*:*:*
quarkus quarkus 3.0.0 cpe:2.3:a:quarkus:quarkus:3.0.0:candidate_release2:*:*:*:*:*:*

References for CVE-2023-5720

cvelogic Threat Intelligence