quarkus-core leaks local environment variables from Quarkus namespace during application's build
Published Apr 4, 2024 · Updated Nov 3, 2026
Original summary
Normalized public record · Updated Nov 3, 2026
quarkus-core leaks local environment variables from Quarkus namespace during application's build
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A vulnerability was found in the quarkus-core component. Quarkus captures the local environment variables from the Quarkus namespace during the application's build. Thus, running the resulting application inherits the values captured at build time.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2024:11023 ↗
- RHSA-2024:2106 ↗
- RHSA-2024:2705 ↗
- RHSA-2024:3527 ↗
- RHSA-2024:4028 ↗
- RHSA-2024:4873 ↗
- access.redhat.com ↗
- RHBZ#2273281 ↗
Record history
Published Apr 4, 2024 · Last refreshed Nov 3, 2026