pgAdmin 4 Path Traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

EPSS

• CVE-2022-0959: 0.97% estimated exploitation activity in the next 30 days; percentile 61.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

When run in server mode, pgAdmin 4 allows users to store files on the server under individual storage directories. Files such as SQL scripts may be uploaded through the user interface. The URI to which upload requests are made fails to validate the upload path to prevent path traversal techniques being used to store files outside of the storage directory. A malicious, but authorised and authenticated user can construct an HTTP request using their existing CSRF token and session cookie to manually upload files to any location that the operating system user account under which pgAdmin is running has permission to write.

Published by the source

17 Mar 2022, 00:00 UTC

Last modified by the source

6 Jul 2026, 08:11 UTC

Source last checked

26 Oct 2026, 13:11 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cr8c-972v-rmp3

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cr8c-972v-rmp3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-0959

Advisory: pgAdmin 4 Path Traversal vulnerability
IDs: CVE-2022-0959, GHSA-cr8c-972v-rmp3
Record: https://patchnext.com/advisories/cve-2022-0959 (revision 2, source checked 26 Oct 2026, 13:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pgadmin4 6.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI pgadmin4: affected < 6.7; fixed in 6.7

## Suggested inspection (read-only)
- `python -m pip show pgadmin4`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pgadmin4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-cr8c-972v-rmp3 (OSV record GHSA-cr8c-972v-rmp3 lists affected ranges: PyPI pgadmin4 >=0 <6.7 (fixed))
- Verified: https://github.com/advisories/GHSA-cr8c-972v-rmp3 (GitHub-reviewed advisory GHSA-cr8c-972v-rmp3 lists affected ranges: PyPI pgadmin4 >=0 <6.7)

Commands are suggestions: review each one before running it.