pgAdmin 4 9.16 Fixes Critical SQL Injection Bugs and Adds Tab Color Coding
The latest update to the leading open source PostgreSQL GUI drops seven security patches alongside a handful of usability tweaks that actually matter. Database administrators who skipped the last few releases should grab this version immediately since it plugs several critical SQL injection and cross site scripting holes that could hand attackers full control over connected servers. This release also introduces tab color coding, middle click tab closing, and finally stops mangling jsonb numbers when saving rows.
Security Patches That Actually Matter
The security fixes in this build cover the kind of vulnerabilities that keep database administrators up at night. Sixteen dialog templates previously rendered raw SQL comments directly into HTML, which meant a crafted description could trigger stored cross site scripting across every connected database. The development team swapped those rendering paths to qtLiteral and now passes relation OIDs through proper type casting instead of string interpolation. There is also a nasty AI Assistant bypass that let prompt injected payloads break out of read only transactions and chain straight to remote code execution via COPY TO PROGRAM on superuser connections. Missing authentication decorators on two SQL Editor endpoints exposed a pickle deserialization sink, while an unvalidated next parameter in the multi factor authentication flow created an open redirect. All of these get patched here, so running this update is less about convenience and more about keeping the database door locked.
Usability Tweaks That Save Time
The feature list leans heavily on small quality of life improvements rather than rewriting the core engine. Panel and tab headers now match the color assigned to each connected server, which cuts down on the classic case of editing a production database while thinking it is a staging instance. Middle clicking a tab title closes it instantly, removing the need to hunt for that tiny close button when managing dozens of query windows. The password reset flow finally gets a back to login link, and OAuth2 buttons can now pull from any Font Awesome style instead of being stuck with brand icons. Cloud deployment modules got a minor HTML injection fix where SDK error text leaked into browser parsers, though EDB BigAnimal support has been quietly removed after last cycle deprecated it.
Under the Hood Changes and Deprecations
Several backend adjustments clean up legacy baggage that tends to cause crashes or bloated installs. The View Edit Data window no longer throws a fatal error when a transaction object lacks filter capabilities, which has been tripping up desktop users after upgrades. JSON editor behavior now preserves exact number formatting, so trailing zeros and large integers stop getting rewritten on save. PostgreSQL 14 is officially the default target version, meaning older template buckets for sub fourteen releases get dropped entirely. The macOS bundle also gets stripped of foreign architecture slices to keep single arch builds lean. On the scheduling front, pgAgent has been deprecated across the board. Support will vanish in about six months and the website files disappear within thirty days, so teams relying on it should start planning a migration to something like pg_cron or an external orchestrator right away.
Installation and Availability
The update ships as a Python wheel, Docker container, RPM package, DEB package, source tarball, and native installers for Windows and macOS. Users who prefer the desktop application should verify their existing server connections after upgrading since the session object fix changes how transaction states load on startup. Helm chart operators can now configure init container security contexts through a dedicated parameter instead of patching manifests manually. The Italian translation received updates across the interface, and core dependencies like Electron and cryptography got bumped to stable releases that align with current system requirements.
Grab the installer from the official download page when ready. The database stays safer when the GUI stops leaving doors wide open.
