GHSA-7g97-7r3c-5cc6 is a low-severity (CVSS 3.5) Information Exposure vulnerability in io.quarkus:quarkus-kubernetes-deployment. A fix is available for io.quarkus:quarkus-kubernetes-deployment — see the affected versions and patch details below.
In Quarkus, git credentials could be inadvertently published
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 GHSA-7g97-7r3c-5cc6.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-7g97-7r3c-5cc6 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.quarkus:quarkus-kubernetes-deploymentReal-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 Quarkus. In certain conditions related to the CI process, git credentials could be inadvertently published, which could put the git repository at risk.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-kubernetes-deployment | all versions | 3.7.3io.quarkus:quarkus-kubernetes-deployment:3.7.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-kubernetes-deployment, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-kubernetes-deployment to 3.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7g97-7r3c-5cc6 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7g97-7r3c-5cc6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7g97-7r3c-5cc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
Three conditions are required to enable this vulnerability: 1) If you are in an environment where you have a token in the Git URL of the Quarkus project you are building 2) If you build with a Quarkus extension that generates a Kubernetes descriptor (for instance a Kubernetes or OpenShift extension) 3) If this…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 3.2.11.Final | io.quarkus/quarkus-kubernetes-deployment:3.2.11.Final-redhat-00001 | RHSA-2024:1662 |
Frequently Asked Questions
Is GHSA-7g97-7r3c-5cc6 in your dependencies?
O3 Security finds GHSA-7g97-7r3c-5cc6 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.