Advisory record · GHSA-f8h5-v2vg-46rr

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

CVSS 7.0 HighEPSS 0.0031 · 23rd percentile

Published by the GitHub Advisory Database at 4 Apr 2024, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
io.quarkus:quarkus-coreMaven>=3.9.0.CR1, <3.9.2 || >=3.3.0.CR1, <3.8.4 || <3.2.12.Final3.9.2, 3.8.4, 3.2.12.Final
Identifiers
GHSA-f8h5-v2vg-46rr · CVE-2024-2700
Weakness (CWE)
CWE-526
Published
4 Apr 2024
Updated
7 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Quarkus core versions from 3.9.0.CR1 before 3.9.2, from 3.3.0.CR1 before 3.8.4, and before 3.2.12.Final are affected by a flaw in quarkus-core. It captures Quarkus-namespace environment variables set in the developer or CI environment during the build and bakes them into the built application, so settings meant only for testing can run in production. Upgrade quarkus-core to 3.9.2, 3.8.4, or 3.2.12.Final. Applications that do not override these values, or that set them through environment variables or .env files, are at risk; the source gives few details on how an attacker would exploit this.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.0 High 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0031, the 23rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 4 Apr 2024, 13:46 UTC Confirmed by the CVE List
  2. 4 Apr 2024, 14:15 UTC Confirmed by NVD
  3. 31 Oct 2026, 14:19 UTC First seen by agentprime
  4. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.