NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2024-2700 — quarkus-core

HIGHFix: quarkusio/quarkus@2b24dc8

CVE-2024-2700 is a high-severity (CVSS 7) CWE-526 vulnerability in io.quarkus:quarkus-core. A fix is available for io.quarkus:quarkus-core — see the affected versions and patch details below.

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

Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-2700.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk
0.00%0.27%0.54%0.81%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
☕io.quarkus:quarkus-core☕io.quarkus:quarkus-core☕io.quarkus:quarkus-core

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

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.quarkus:quarkus-core≥ 3.9.0.CR1&&< 3.9.23.9.2io.quarkus:quarkus-core:3.9.2
☕Mavenio.quarkus:quarkus-core≥ 3.3.0.CR1&&< 3.8.43.8.4io.quarkus:quarkus-core:3.8.4
☕Mavenio.quarkus:quarkus-coreall versions3.2.12.Finalio.quarkus:quarkus-core:3.2.12.Final

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.quarkus:quarkus-core to 3.9.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-2700 is resolved across your whole dependency graph.

  3. Workarounds

    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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat rates this as a Moderate impact vulnerability since this requires an attacker to have direct access to the environment variables to override, and the application must use that environment variable to be jeopardized.

ProductFixed inAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4quarkus-coreRHSA-2024:11023
Red Hat AMQ Streams 2.7.0see advisoryRHSA-2024:3527
Red Hat build of Apicurio Registry 2.6.1 GAquarkus-coreRHSA-2024:4873
Red Hat build of Quarkus 3.2.12.Finalio.quarkus/quarkus-core:3.2.12.Final-redhat-00001RHSA-2024:2705
Red Hat build of Quarkus 3.8.4.redhatio.quarkus/quarkus-core:3.8.4.redhat-00002RHSA-2024:2106
RHOSS-1.33-RHEL-8openshift-serverless-1/client-kn-rhel8:1.12.0-4RHSA-2024:4028

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is CVE-2024-2700 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-2700: quarkus-core — Fixed in 3.9.2