dbcve.org
Pgadmin 4Application · Pgadmin

CVE-2025-9636

HIGH · 7.9 CVSS v3.1 Published 2025-09-04
Fix available
A fix is available. Upgrade to after 9.7 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

pgAdmin versions 9.7 and below lack proper Cross-Origin Opener Policy (COOP) headers in their HTTP responses. This allows malicious cross-origin pages to maintain a reference to the victim's window, enabling attackers to manipulate the OAuth authentication flow through opener window interactions. The vulnerability enables session hijacking and account takeover by intercepting or redirecting OAuth callbacks.

MitigationUpgrade pgAdmin to version 9.8 or later. If upgrading is not immediately feasible, implement proper COOP headers (e.g., 'Cross-Origin-Opener-Policy: same-origin') on the OAuth endpoints and ensure the OAuth redirect URI validation is strict.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pgadmin 4Application
Affected:<= 9.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed pgAdmin version
    Access the pgAdmin dashboard, go to 'Help' > 'About' or check the server log at startup for the version number. If using pip, run: pip show pgadmin4
    Affected if Version is 9.7 or below (versions 9.8+ contain the fix)
  2. Verify OAuth authentication is configured
    Check if pgAdmin is configured to use OAuth by examining the config_local.py or config_system.py files for OAuth-related settings (e.g., 'OAUTH2_CONFIG', 'AUTHENTICATION_SOURCES'). Alternatively, check the pgAdmin server runtime settings for enabled authentication methods.
    Affected if OAuth authentication is enabled as an authentication source
  3. Inspect HTTP response headers for COOP
    Use a browser developer tool or curl to make a request to the pgAdmin OAuth endpoint (typically /oauth2/authorize or the login page) and examine response headers: curl -I https://<pgadmin-url>/oauth2/authorize. Look for the 'Cross-Origin-Opener-Policy' header.
    Affected if The Cross-Origin-Opener-Policy header is absent or not set to 'same-origin' on OAuth-related endpoints
  4. Check OAuth redirect URI configuration
    Review the OAuth configuration in config_local.py or config_system.py for 'OAUTH2_REDIRECT_URL' and any allowed redirect URI patterns. Validate that strict redirect URI validation is implemented.
    Affected if OAuth redirect URI validation is permissive or missing, allowing arbitrary redirect URIs

A user is affected if pgAdmin 9.7 or below is running with OAuth authentication enabled and the HTTP responses lack Cross-Origin-Opener-Policy headers on OAuth endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 9.7
Interim mitigation

Upgrade pgAdmin to version 9.8 or later. If upgrading is not immediately feasible, implement proper COOP headers (e.g., 'Cross-Origin-Opener-Policy: same-origin') on the OAuth endpoints and ensure the OAuth redirect URI validation is strict.

Fix this in Pgadmin 4 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9636 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data