{"id":"CVE-2026-116242","aliases":[],"cve":{"records":[{"id":"CVE-2026-116242","source":"PostgreSQL","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-10-25T16:26:16.419Z","published":"2026-10-30T19:55:13.843Z","modified":"2026-10-30T19:55:13.843Z"}],"publishers":[{"name":"PostgreSQL","role":"CNA","organizationId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","modified":"2026-10-30T19:55:13.843Z"}],"references":[{"url":"https://github.com/pgadmin-org/pgadmin4/issues/10662","tags":["issue-tracking"],"source":"PostgreSQL"},{"url":"https://github.com/pgadmin-org/pgadmin4/commit/d52fe4740eb1af89d940f2e412bd66a0a89f08bb","tags":["patch"],"source":"PostgreSQL"}],"weaknesses":[{"id":"CWE-522","description":"CWE-522 Insufficiently Protected Credentials","source":"PostgreSQL"},{"id":"CWE-1188","description":"CWE-1188 Initialization of a Resource with an Insecure Default","source":"PostgreSQL"}],"applicability":[],"prioritization":[]},"title":"pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity","titleSource":"PostgreSQL","descriptionSource":"PostgreSQL","description":"pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account's ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account's key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.\n\nThe fix makes tunnels in server mode use only the identity file or password the user configured: the service account's keys, configuration and agent are no longer used, and an identity file that cannot be found in the user's storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.\n\nThis issue affects pgAdmin 4: before 9.19.","score":8.2,"severity":"high","published":"2026-10-30T19:55:13.843Z","modified":"2026-10-30T19:55:13.843Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"pgadmin.org","name":"pgAdmin 4","platforms":[],"versions":[{"version":"0","status":"affected","lessThan":"9.19","versionType":"custom"}],"defaultStatus":"unaffected","cpes":[],"source":"PostgreSQL","url":"https://www.cve.org/CVERecord?id=CVE-2026-116242"}],"remediation":[],"references":["https://github.com/pgadmin-org/pgadmin4/issues/10662","https://github.com/pgadmin-org/pgadmin4/commit/d52fe4740eb1af89d940f2e412bd66a0a89f08bb"],"sources":[{"name":"CVE","id":"CVE-2026-116242","modified":"2026-10-30T19:55:13.843Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-116242"}],"assessments":[{"source":"PostgreSQL","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N","score":8.2},{"source":"PostgreSQL","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N","score":7.1}],"sourceAffected":[],"observedAt":"2026-10-30T20:24:35.731Z","kev":{"status":"not-listed","checkedAt":"2026-10-31T09:10:30.844Z"},"coverage":[{"source":"NVD","status":"not-checked"},{"source":"GHSA","status":"not-checked"},{"source":"EUVD","status":"not-checked"},{"source":"EPSS","status":"not-checked"}],"evidence":[],"aiSummary":{"text":"pgAdmin 4, before version 9.19, uses the service account's SSH identity when opening SSH tunnels, allowing any user to configure a tunnel to a host that accepts the service account's key. The vulnerability requires access to the pgAdmin service account. It is related to insufficiently protected credentials and insecure default initialization.","model":"@cf/meta/llama-3.3-70b-instruct-fp8-fast","generatedAt":"2026-10-31T05:21:07.710Z","sources":[{"name":"CVE","url":"https://www.cve.org/CVERecord?id=CVE-2026-116242"}]}}