quarkus-core leaks local environment variables from Quarkus namespace during application's build

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.0 · CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2024-2700: 0.31% estimated exploitation activity in the next 30 days; percentile 23.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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. However, some local environment variables may have been set by the developer / CI environment for testing purposes, such as dropping the database during the application startup or trusting all TLS certificates to accept self-signed certificates. If these properties are configured using environment variables or the .env facility, they are captured into the built application. It may lead to dangerous behavior if the application does not override these values. This behavior only happens for configuration properties from the quarkus. namespace. So, application-specific properties are not captured.

Published by the source

4 Apr 2024, 15:30 UTC

Last modified by the source

13 Dec 2024, 00:31 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f8h5-v2vg-46rr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-2700

Advisory: quarkus-core leaks local environment variables from Quarkus namespace during application's build
IDs: CVE-2024-2700, GHSA-f8h5-v2vg-46rr
Record: https://patchnext.com/advisories/cve-2024-2700 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.quarkus:quarkus-core 3.9.2, 3.8.4, 3.2.12.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.quarkus:quarkus-core: affected >= 3.9.0.CR1, <= 3.9.1; >= 3.3.0.CR1, <= 3.8.3; < 3.2.12.Final; fixed in 3.2.12.Final, 3.9.2, 3.8.4

## Suggested inspection (read-only)
- Maven io.quarkus:quarkus-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.quarkus:quarkus-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f8h5-v2vg-46rr (GitHub-reviewed advisory GHSA-f8h5-v2vg-46rr lists affected ranges: Maven io.quarkus:quarkus-core >=3.9.0.CR1 =3.3.0.CR1 =0 <3.2.12.Final)

Commands are suggestions: review each one before running it.