CVE-2026-7813

{"id": "CVE-2026-7813", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-7813", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "no"}, {"technicalImpact": "total"}], "version": "2.0.3", "timestamp": "2026-05-11T17:32:45.774855Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.9, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 6.0, "exploitabilityScore": 3.1}], "cvssMetricV40": [{"type": "Secondary", "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.4, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "NONE", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "affected": [{"source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007", "affectedData": [{"repo": "https://github.com/pgadmin-org/pgadmin4", "vendor": "pgadmin.org", "modules": ["Server Mode", "Shared Servers", "Background Processes", "Debugger"], "product": "pgAdmin 4", "versions": [{"status": "affected", "version": "0", "lessThan": "9.15", "versionType": "custom"}], "programFiles": ["https://github.com/pgadmin-org/pgadmin4/blob/master/web/pgadmin/browser/server_groups/servers/__init__.py", "https://github.com/pgadmin-org/pgadmin4/blob/master/web/pgadmin/utils/driver/psycopg3/__init__.py", "https://github.com/pgadmin-org/pgadmin4/blob/master/web/pgadmin/model/__init__.py"], "defaultStatus": "affected"}]}], "published": "2026-05-11T16:17:37.470", "references": [{"url": "https://github.com/pgadmin-org/pgadmin4/pull/9830", "tags": ["Issue Tracking", "Patch"], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007"}, {"url": "https://github.com/pgadmin-org/pgadmin4/pull/9835", "tags": ["Issue Tracking", "Patch"], "source": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-284"}]}], "descriptions": [{"lang": "en", "value": "Authorization vulnerability in pgAdmin 4 server mode affecting Server Groups, Servers, Shared Servers, Background Processes, and Debugger modules.\n\nMultiple endpoints fetched user-owned objects without filtering by the requesting user's identity. An authenticated user could access another user's private servers, server groups, background processes, and debugger function arguments by guessing object IDs.\n\nAdditionally, the Shared Servers feature contained multiple issues including credential leakage (passexec_cmd, passfile, SSL keys), privilege escalation via writable passexec_cmd (a shell command executed when establishing the connection) allowing arbitrary command execution in the owner's process context, and owner-data corruption via SQLAlchemy session mutations. Several owner-only fields (passexec_cmd, passexec_expiration, db_res, db_res_type) were writable by non-owners through the API, and additional fields (kerberos_conn, tags, post_connection_sql) lacked per-user persistence so non-owner edits mutated the owner's record.\n\nFix centralises access control via a new server_access module, scopes all user-owned models with a UserScopedMixin, returns HTTP 410 from connection_manager when access is denied in server mode, suppresses owner-only fields for non-owners across the merge / API response / ServerManager paths, and adds an explicit owner-only write guard. The remediation landed in two pull requests; both are referenced.\n\nThis issue affects pgAdmin 4: before 9.15."}, {"lang": "es", "value": "Vulnerabilidad de autorizaci\u00f3n en el modo de servidor de pgAdmin 4 que afecta a los m\u00f3dulos de Grupos de Servidores, Servidores, Servidores Compartidos, Procesos en Segundo Plano y Depurador.\n\nM\u00faltiples puntos finales obtuvieron objetos propiedad del usuario sin filtrar por la identidad del usuario solicitante. Un usuario autenticado podr\u00eda acceder a los servidores privados de otro usuario, grupos de servidores, procesos en segundo plano y argumentos de funciones del depurador adivinando los ID de los objetos.\n\nAdem\u00e1s, la funci\u00f3n de Servidores Compartidos conten\u00eda m\u00faltiples problemas, incluida la fuga de credenciales (passexec_cmd, passfile, claves SSL), escalada de privilegios a trav\u00e9s de passexec_cmd escribible (un comando de shell ejecutado al establecer la conexi\u00f3n) permitiendo la ejecuci\u00f3n arbitraria de comandos en el contexto del proceso del propietario, y la corrupci\u00f3n de datos del propietario a trav\u00e9s de mutaciones de la sesi\u00f3n de SQLAlchemy. Varios campos solo para el propietario (passexec_cmd, passexec_expiration, db_res, db_res_type) eran escribibles por no propietarios a trav\u00e9s de la API, y campos adicionales (kerberos_conn, tags, post_connection_sql) carec\u00edan de persistencia por usuario, por lo que las ediciones de no propietarios mutaban el registro del propietario.\n\nLa correcci\u00f3n centraliza el control de acceso a trav\u00e9s de un nuevo m\u00f3dulo server_access, establece el alcance de todos los modelos propiedad del usuario con un UserScopedMixin, devuelve HTTP 410 desde connection_manager cuando se deniega el acceso en modo de servidor, suprime los campos solo para el propietario para los no propietarios en las rutas de fusi\u00f3n / respuesta de la API / ServerManager, y a\u00f1ade una protecci\u00f3n de escritura expl\u00edcita solo para el propietario. La remediaci\u00f3n se implement\u00f3 en dos solicitudes de extracci\u00f3n; ambas est\u00e1n referenciadas.\n\nEste problema afecta a pgAdmin 4: anterior a 9.15."}], "lastModified": "2026-10-26T18:10:00.173", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:pgadmin:pgadmin_4:*:*:*:*:*:postgresql:*:*", "vulnerable": true, "matchCriteriaId": "E4868FB7-72D2-466C-B535-DD5CF92A8D5F", "versionEndExcluding": "9.15"}], "operator": "OR"}]}], "sourceIdentifier": "f86ef6dc-4d3a-42ad-8f28-e6d5547a5007"}