CVE-2026-104055: Canonical postgresql-operator · Sensitive Data in Logs
Affects Canonical postgresql-operatorSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 1217 : update Canonical postgresql-operator when convenient.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1217, 1216, 1190 +1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade postgresql-operator and charmed-postgresql to 1217, 1216, 1190 or 1189.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Canonicalpostgresql-operator | Affected
| Fixed in
|
| Canonicalpostgresql-operator | Affected
| Fixed in
|
| Canonicalpostgresql-operator | Affected
| Fixed in
|
| Canonicalpostgresql-operator | Affected
| Fixed in
|
GitHubcharmed-postgresqlpkg:github/charmed-postgresqlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The vulnerability is fixed in the following revisions: 1189 (arm64) and 1190 (amd64) on the dev track (14/edge), and 1216 (arm64) and 1217 (amd64) on the stable track (14/stable). Users should upgrade to these or later revisions to remediate the issue.
Description
The postgresql-operator charm runs a Prometheus postgres_exporter to collect database metrics using a dedicated "monitoring" PostgreSQL user. On database connection errors, the exporter writes the monitoring user's password in cleartext to its logs. Any actor able to read those logs can recover the password, which grants read-only pg_monitor access to PostgreSQL. This is fixed in the dev track (14/edge) in revisions 1189 (arm64) and 1190 (amd64), and in the stable track (14/stable) in revisions 1216 (arm64) and 1217 (amd64).
References
- github.com/canonical/postgresql-operator/security/advisories/GHSA-rcx7-7rh5-r542 (opens in a new tab)
- github.com/canonical/postgresql-operator/pull/1863 (opens in a new tab)
- github.com/canonical/charmed-postgresql-snap/pull/305 (opens in a new tab)
- github.com/canonical/charmed-postgresql-snap/pull/307 (opens in a new tab)