CVE-2026-104055 Canonical CVE debrief

Who should care

Defenders responsible for charmed-postgresql-snap and postgresql-operator deployments, particularly those using the monitoring PostgreSQL user, should assess exposure and apply fixes.

Why it matters

CVE-2026-104055 allows actors with log access to recover the monitoring user's password, granting read-only access to PostgreSQL. Defenders should verify exposure, apply fixes, review logs, and consider compensating controls.

• Defenders need to verify if the postgresql-operator charm is used in their environment and if the monitoring PostgreSQL user is enabled.
• Potential exposure of the monitoring user's password in logs requires review and possible rotation of credentials.
• Fixes are available in specific revisions for dev and stable tracks, requiring updates to prevent future exposure.
• Compensating controls, such as log access restrictions and monitoring, may be necessary to mitigate potential impacts.

Technical summary

The postgresql-operator charm uses a Prometheus postgres_exporter to collect database metrics with a dedicated 'monitoring' PostgreSQL user. On database connection errors, the exporter logs the monitoring user's password in cleartext. This issue allows any actor with access to the logs to recover the password, granting read-only pg_monitor access to PostgreSQL. The postgresql-operator charm writes the monitoring user's password in cleartext to logs on database connection errors. Fixes are available in revisions 1189 (arm64) and 1190 (amd64) for the dev track, and revisions 1216 (arm64) and 1217 (amd64) for the stable track. The issue requires defenders to verify exposure, apply fixes, review logs, and consider

Defensive priority

Defenders should prioritize verifying exposure and applying fixes for the postgresql-operator charm, particularly in environments using the monitoring PostgreSQL user.

Recommended defensive actions

• Verify if the postgresql-operator charm is used in your environment and if the monitoring PostgreSQL user is enabled.
• Check the current revision of the charm and update to a fixed revision if necessary.
• Review logs for potential exposure of the monitoring user's password.
• Consider compensating controls, such as restricting access to logs and monitoring for suspicious activity.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source references indicate that the postgresql-operator charm writes the monitoring user's password in cleartext to logs on database connection errors. Fixes are available in revisions 1189 (arm64) and 1190 (amd64) for the dev track, and revisions 1216 (arm64) and 1217 (amd64) for the stable track.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.