Skip to main content
VulnerabilityPublished Updated

CVE-2025-9636: pgAdmin 4 · CWE-346

Affects pgAdmin 4Source CVE Database V5

0

Not known to be exploited · CVSS 7.9 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
pgadmin.org pgAdmin 4Affected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2025-9636, organizations should first monitor pgAdmin.org and related PostgreSQL security advisories for official patches and apply them promptly upon release. Until patches are available, administrators should consider restricting access to pgAdmin 4 interfaces via network segmentation, VPNs, or IP whitelisting to limit exposure. Implementing strict Content Security Policy (CSP) headers and verifying COOP and Cross-Origin Resource Policy (CORP) settings can help reduce cross-origin attack surfaces. Review and harden OAuth configurations, including redirect URIs and token scopes, to minimize the impact of manipulated flows. Educate users about phishing risks and the importance of cautious interaction with OAuth prompts. Employ multi-factor authentication (MFA) where possible to add an additional security layer. Regularly audit pgAdmin user accounts and permissions to detect unusual activity. Consider alternative database management tools temporarily if risk tolerance is low. Finally, maintain comprehensive logging and monitoring to detect exploitation attempts early.

Description

pgAdmin <= 9.7 is affected by a Cross-Origin Opener Policy (COOP) vulnerability. This vulnerability allows an attacker to manipulate the OAuth flow, potentially leading to unauthorised account access, account takeover, data breaches, and privilege escalation.

References

Community reviews

Loading reviews…