PgAdmin Vulnerability Allows Attackers to Gain Unauthorized Account Access
Cybersecurity Update: pgAdmin4 Vulnerability Disclosure
A recently identified security vulnerability in pgAdmin4, an open-source tool for managing PostgreSQL databases, has been disclosed. This vulnerability, designated as CVE-2025-9636 and classified as high severity, has significant implications for developers and database administrators.
Technical Specifications
The vulnerability is a Cross-Origin Opener Policy (COOP) flaw affecting pgAdmin versions up to 9.7. It can be exploited during the authentication and OAuth flow, potentially leading to unauthorized access, session hijacking, and account takeover.
Impact
Exploiting this vulnerability could compromise sensitive data, escalate user privileges, and facilitate further cyberattacks on connected systems. Administrators using pgAdmin for critical tasks like database configuration and query management are particularly at risk.
Vulnerability Details
The vulnerability requires user interaction but poses a significant risk due to the role pgAdmin plays in PostgreSQL environments. By manipulating COOP headers, malicious actors can bypass browser protections, allowing unauthorized access.
| Field | Details |
| CVE ID | CVE-2025-9636 |
| GitHub Advisory ID | GHSA-6859-2qxq-ffv2 |
| Severity | High |
| Affected Versions | pgAdmin ≤ 9.7 |
| Patched Version | 9.8 |
| Vulnerability Type | Cross-Origin Opener Policy (COOP) flaw |
The CVSS v3.1 score reflects a severe impact on confidentiality and integrity, with moderate effects on availability. The pgAdmin development team has released a patched version, 9.8, to address the issue.
Recommendations
Users are advised to upgrade to the patched version immediately. Additionally, reviewing current sessions, auditing access logs, and considering credential rotation are recommended steps.
Security researchers stress the importance of maintaining an updated environment and monitoring log activity to defend against potential exploits.
This vulnerability underscores the need for continued vigilance and timely application of security patches, particularly as pgAdmin’s role in managing PostgreSQL environments continues to grow.