# CVE-2026-104055: Monitoring-user password logged in cleartext by postgres_exporter in postgresql VM charm

> Attackers with log access can recover cleartext monitoring passwords, gaining read-only database access in PostgreSQL operator charms.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 3 Oct 2026
- **Also known as:** GHSA-3533-w4pf-7x2r, GHSA-rcx7-7rh5-r542

## What is CVE-2026-104055?

CVE-2026-104055 is a medium-severity vulnerability in Canonical postgresql-operator, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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).

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-104055?


## How do I fix CVE-2026-104055?

No fix has been published for CVE-2026-104055 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104055 being exploited?

There is no known exploitation of CVE-2026-104055 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104055 and fix it if it is affected.

What it is: CVE-2026-104055 is a medium-severity vulnerability in Canonical postgresql-operator, published on 2 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-104055 in the wild and no public exploit code.

Affected product: Canonical postgresql-operator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104055/ (Markdown: https://insights.sbomify.com/CVE-2026-104055/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104055
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104055
- OSV: https://osv.dev/vulnerability/CVE-2026-104055

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104055/
Summaries are generated and may contain mistakes; the official description above is the record.