Quick answers
- Is CVE-2026-104055 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104055 being exploited in the wild.
- How severe is CVE-2026-104055?
- Informational severity, published 2 October 2026.
- Which products and versions are affected?
- Canonical Postgresql-Operator Charm 14/stable prior to revisions 1216 (arm64) and 1217 (amd64); 14/edge prior to revisions 1189 (arm64) and 1190 (amd64).
- Is there a fix for CVE-2026-104055?
- Yes: fixed in 14/stable revisions 1216 (arm64) and 1217 (amd64); 14/edge revisions 1189 (arm64) and 1190 (amd64). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104055 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-104055?
- Check whether you run Canonical Postgresql-Operator Charm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 14/stable revisions 1216 (arm64) and 1217 (amd64); 14/edge revisions 1189 (arm64) and 1190 (amd64)
Technical details
The postgres_exporter component logs the monitoring user password in cleartext upon database connection failures, allowing anyone with log file access to extract credentials. The vulnerability requires local or administrative access to read application logs. The issue has been fixed by switching away from legacy data source format in the exporter configuration.
Affected products
- Canonical postgresql-operator charm 14/stable prior to revisions 1216 (arm64) and 1217 (amd64); 14/edge prior to revisions 1189 (arm64) and 1190 (amd64)
Timeline
- 2026-10-02: disclosed