Zitadel exposing internal database user name and host informationGHSA-q5qj-x2h5-3945
MEDIUMFix: zitadel/zitadel@b918603GHSA-q5qj-x2h5-3945 is a medium-severity (CVSS 5.3) Information Exposure vulnerability in github.com/zitadel/zitadel. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-q5qj-x2h5-3945.
EPSS Exploitation Probability
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
github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadelReal-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
Impact
In case ZITADEL could not connect to the database, connection information including db name, username and db host name could be returned to the user.
Patches
2.x versions are fixed on >= 2.50.3 2.49.x versions are fixed on >= 2.49.5 2.48.x versions are fixed on >= 2.48.5 2.47.x versions are fixed on >= 2.47.10 2.46.x versions are fixed on >= 2.46.7 2.45.x versions are fixed on >= 2.45.7
Workarounds
There is no workaround since a patch is already available.
Questions
If you have any questions or comments about this advisory, please email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.50.0&&< 2.50.3 | 2.50.3go get github.com/zitadel/zitadel@v2.50.3 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.49.0&&< 2.49.5 | 2.49.5go get github.com/zitadel/zitadel@v2.49.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.48.0&&< 2.48.5 | 2.48.5go get github.com/zitadel/zitadel@v2.48.5 |
| 🐹Go | github.com/zitadel/zitadel | ≥ 2.47.0&&< 2.47.10 | 2.47.10go get github.com/zitadel/zitadel@v2.47.10 |
| 🐹Go | github.com/zitadel/zitadel | all versions | 2.45.7go get github.com/zitadel/zitadel@v2.45.7 |
Affected Products
zitadelzitadelDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/zitadel/zitadel to 2.50.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q5qj-x2h5-3945 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-q5qj-x2h5-3945 in your dependencies?
Find it across Go, including transitive dependencies.