CVE-2025-2506
When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglogical command to obtain read access to replicated tables. When pglogical runs it should verify it is running on a replication connection but does not perform this check. This vulnerability was introduced in the pglogical 3.x codebase, which is proprietary to EDB. The same code base has been integrated into BDR/PGD 4 and 5. To exploit the vulnerability the attacker needs at least CONNECT permissions to a database configured for replication and must understand a number of pglogical3/BDR specific commands and be able to decode the binary protocol.
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
- Puntuación base: 5.3
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.31%
- Percentil entre todas las CVEs puntuadas: 22
- Fecha de la puntuación: 5/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (3)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
CWE
- CWE-862
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2025-2506",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-2506",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2025-05-22T15:28:11.313435Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 5.3,
"attackVector": "NETWORK",
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
"integrityImpact": "NONE",
"userInteraction": "NONE",
"attackComplexity": "HIGH",
"availabilityImpact": "NONE",
"privilegesRequired": "LOW",
"confidentialityImpact": "HIGH"
},
"impactScore": 3.6,
"exploitabilityScore": 1.6
}
]
},
"affected": [
{
"source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
"affectedData": [
{
"vendor": "EnterpriseDB",
"product": "pglogical",
"versions": [
{
"status": "affected",
"version": "3",
"lessThan": "3.7.26-ELS",
"versionType": "custom"
}
],
"defaultStatus": "affected"
},
{
"vendor": "EnterpriseDB",
"product": "BDR/PGD",
"versions": [
{
"status": "affected",
"version": "4",
"lessThan": "4.3.8-ELS",
"versionType": "custom"
}
],
"defaultStatus": "affected"
},
{
"vendor": "EnterpriseDB",
"product": "BDR/PGD",
"versions": [
{
"status": "affected",
"version": "5",
"lessThan": "5.8.0",
"versionType": "custom"
}
],
"defaultStatus": "affected"
}
]
}
],
"published": "2025-05-22T16:15:54.010",
"references": [
{
"url": "https://www.enterprisedb.com/docs/security/advisories/cve20252506/",
"source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659"
}
],
"vulnStatus": "Deferred",
"weaknesses": [
{
"type": "Secondary",
"source": "20be33e2-bf35-4d13-8fad-18bd2f3e3659",
"description": [
{
"lang": "en",
"value": "CWE-862"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglogical command to obtain read access to replicated tables. When pglogical runs it should verify it is running on a replication connection but does not perform this check. This vulnerability was introduced in the pglogical 3.x codebase, which is proprietary to EDB. The same code base has been integrated into BDR/PGD 4 and 5.\nTo exploit the vulnerability the attacker needs at least CONNECT permissions to a database configured for replication and must understand a number of pglogical3/BDR specific commands and be able to decode the binary protocol."
},
{
"lang": "es",
"value": "Cuando pglogical intenta replicar datos, no verifica si está utilizando una conexión de replicación. Esto significa que un usuario con acceso CONNECT a una base de datos configurada para replicación puede ejecutar el comando pglogical para obtener acceso de lectura a las tablas replicadas. Al ejecutarse, pglogical debería verificar si está ejecutándose en una conexión de replicación, pero no realiza esta comprobación. Esta vulnerabilidad se introdujo en el código base de pglogical 3.x, propiedad de EDB. Este mismo código base se ha integrado en BDR/PGD 4 y 5. Para explotar esta vulnerabilidad, el atacante necesita al menos permisos CONNECT a una base de datos configurada para replicación, comprender varios comandos específicos de pglogical3/BDR y ser capaz de decodificar el protocolo binario."
}
],
"lastModified": "2026-06-17T09:07:04.890",
"sourceIdentifier": "20be33e2-bf35-4d13-8fad-18bd2f3e3659"
}