Logging of the firestore key within nodejs-firestore
Published Dec 4, 2023 · Updated Oct 23, 2026 · Also known as GHSA-4g6q-77j7-vvjc
Original summary
Normalized public record · Updated Oct 23, 2026
Logging of the firestore key within nodejs-firestore
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
A potential logging of the firestore key via logging within nodejs-firestore exists - Developers who were logging objects through this._settings would be logging the firestore key as well potentially exposing it to anyone with logs read access. We recommend upgrading to version 6.1.0 to avoid this issue
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- GHSA-4g6q-77j7-vvjc
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
Record history
Published Dec 4, 2023 · Last refreshed Oct 23, 2026