GHSA-v34r-vj4r-38j6 is a high-severity (CVSS 7.1) CWE-359 vulnerability in github.com/updatecli/updatecli. A fix is available for github.com/updatecli/updatecli — see the affected versions and patch details below.
Updatecli exposes Maven credentials in console output
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v34r-vj4r-38j6.
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-v34r-vj4r-38j6 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,636 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
github.com/updatecli/updatecliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Private maven repository credentials leaked in application logs in case of unsuccessful retrieval operation.
Details
During the execution of an updatecli pipeline which contains a maven source configured with basic auth credentials, the credentials are being leaked in the application execution logs in case of failure.
Credentials are properly sanitized when the operation is successful but not when for whatever reason there is a failure in the maven repository .e.g. wrong coordinates provided, not existing artifact or version.
PoC
The documentation currently state to provide user credentials as basic auth inside the repository field. e.g.
sources:
default:
kind: maven
spec:
repository: "{{ requiredEnv "MAVEN_USERNAME" }}:{{ requiredEnv "MAVEN_PASS" }}@repo.example.org/releases"
groupid: "org.example.company"
artifactid: "my-artifact"
versionFilter:
kind: regex
pattern: "^23(\.[0-9]+){1,2}$"
Logs are sanitized properly in case of a successful operation:
source: source#default
-----------------------------------------------------------
Searching for version matching pattern "^23(\\.[0-9]+){1,2}$"
✔ Latest version is 23.4.0 on the Maven repository at https://repo.example.org/releases/org/example/company/my-artifact/maven-metadata.xml
but leaks credentials in case the GAV coordinates are wrong (misspelled package name or missing):
source: source#default
-----------------------------------------------------------
ERROR: ✗ getting latest version: URL "https://REDACTED:[email protected]/releases/org/example/company/wrong-artifact/maven-metadata.xml" not found or in error
Impact
User credentials/token used to authenticate against a private maven repository can be leaked in clear-text in console or CI logs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/updatecli/updatecli | all versions | 0.93.0go get github.com/updatecli/updatecli@v0.93.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/updatecli/updatecli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/updatecli/updatecli to 0.93.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v34r-vj4r-38j6 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-v34r-vj4r-38j6 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-v34r-vj4r-38j6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v34r-vj4r-38j6 in your dependencies?
O3 Security finds GHSA-v34r-vj4r-38j6 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.