How pgAdmin 4 Is Updated and What Its Releases Include

Updated

pgAdmin 4 ships as numbered releases on an ongoing cadence, and each release bundles bug fixes, new features, and — when needed — security patches. The project publishes a release announcement plus detailed release notes for every version, so you can track exactly what changed before you upgrade. The most recent example in the project's news feed is pgAdmin 4 v9.18, announced September 17, 2026, which included 29 bug fixes and new features along with fixes for four security vulnerabilities (CVE-2026-86861 through CVE-2026-86864).

How releases are structured

Each version announcement follows a consistent pattern:

  • A version number in the form v9.x (for example, v9.18), indicating a point release on the current major line.
  • A count of changes, such as "29 bug fixes and new features."
  • Security disclosures, listed by CVE identifier when the release addresses vulnerabilities.
  • A "notable changes" section that highlights the most user-visible items, split into Features and other categories.
  • A pointer to the full release notes for the complete change list.

The announcement itself is a summary; the release notes are where the exhaustive detail lives. If you need to know whether a specific bug or feature is in a given build, the release notes are the authoritative source.

What a release can contain

Using v9.18 as a concrete example, the notable changes spanned both usability and security:

Features

  • Collapse and restore the Object Explorer by re-clicking the current workspace icon, similar to the VS Code sidebar, with the choice remembered across refreshes.
  • A keyboard shortcut (Ctrl+Alt+B by default) that performs the same toggle, configurable through a new toggle_object_explorer preference.

Security hardening

  • The default Content-Security-Policy was tightened so inline scripts run under a per-request nonce rather than a blanket 'unsafe-inline'.

This mix is typical: interface refinements and preference additions sit alongside security work in the same release.

How to track updates

Two project pages carry the update trail:

Source What it gives you
News / announcements Release announcements with version number, date, change count, CVE list, and notable changes
Release notes The full, itemized list of fixes and features for that version

The news archive keeps past announcements, so you can review the release history rather than only the latest version. The website also links to the release notes directly from each announcement.

Why the cadence matters for you

Because fixes and security patches arrive together in numbered releases, the practical takeaway is:

  • If you maintain a pgAdmin installation, check the announcement for the version you're running and read the security section — CVE fixes are called out explicitly.
  • If you're evaluating a feature, confirm it appears in the "notable changes" or release notes for the version you plan to install, rather than assuming it exists in all builds.
  • If you need the complete picture, go past the announcement to the release notes; the announcement intentionally summarizes.

The project describes pgAdmin as the leading open-source graphical management tool for PostgreSQL, and this release-and-notes structure is how that tool's changes reach users.