CVE-2026-55765

{"id": "CVE-2026-55765", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-55765", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-08-25T15:29:09.334896Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "HIGH", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 1.8}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "cloudnative-pg", "product": "cloudnative-pg", "versions": [{"status": "affected", "version": "< 1.28.4"}, {"status": "affected", "version": ">= 1.29.0, < 1.29.2"}]}]}], "published": "2026-08-20T22:17:22.487", "references": [{"url": "https://github.com/cloudnative-pg/cloudnative-pg/commit/2f0342747e1f160425b9d51753c0069b0d6117d5", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/commit/3cd5af5d388c26758acf13c19ea806b4bcebb3fe", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/commit/9a13573dbe3d78721b7ea92141e6d2324a2c0ef0", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/pull/10724", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.28.4", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.29.2", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.30.0", "source": "security-advisories@github.com"}, {"url": "https://github.com/cloudnative-pg/cloudnative-pg/security/advisories/GHSA-w3gf-xc94-wvmj", "source": "security-advisories@github.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-256"}, {"lang": "en", "value": "CWE-522"}]}], "descriptions": [{"lang": "en", "value": "CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.28.4 and 1.29.2, CloudNativePG embedded cleartext role passwords in `ALTER ROLE` and `CREATE ROLE` statements generated by SetUserPassword in pkg/management/postgres/utils/roles.go and appendPasswordOption in internal/management/controller/roles/postgres.go. When pg_stat_statements was preloaded with track_utility enabled and an untrusted tenant held pg_monitor or pg_read_all_stats, the tenant could recover platform-managed superuser or application-owner passwords, reconnect through enabled superuser TCP access, and execute operating system commands in the database pod with `COPY ... FROM PROGRAM`. Clusters using SCRAM-SHA-256 verifiers in managed-role Secrets were not affected. This issue is fixed in versions 1.28.4, 1.29.2, and 1.30.0."}, {"lang": "es", "value": "CloudNativePG es una plataforma dise\u00f1ada para gestionar bases de datos PostgreSQL dentro de entornos Kubernetes. Antes de las versiones 1.28.4 y 1.29.2, CloudNativePG incrustaba contrase\u00f1as de rol en texto claro en las sentencias \u201cALTER ROLE\u201d y \u201cCREATE ROLE\u201d generadas por SetUserPassword en pkg/management/postgres/utils/roles.go y appendPasswordOption en internal/management/controller/roles/postgres.go. Cuando pg_stat_statements se precargaba con track_utility habilitado y un inquilino no confiable pose\u00eda pg_monitor o pg_read_all_stats, el inquilino pod\u00eda recuperar contrase\u00f1as de superusuario o de propietario de aplicaci\u00f3n gestionadas por la plataforma, reconectarse a trav\u00e9s del acceso TCP de superusuario habilitado y ejecutar comandos del sistema operativo en el pod de la base de datos con \u201cCOPY ... FROM PROGRAM\u201d. Los cl\u00fasteres que utilizaban verificadores SCRAM-SHA-256 en Secrets de rol gestionado no se vieron afectados. Este problema est\u00e1 solucionado en las versiones 1.28.4, 1.29.2 y 1.30.0."}], "lastModified": "2026-10-26T10:10:00.140", "sourceIdentifier": "security-advisories@github.com"}