A shell injection flaw was found in pglogical in versions before 2.3.4 and before 3.6.26.

published 2021-06-01 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-26833

cvss: 6.7; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits: 0; none known

A shell injection flaw was found in pglogical in versions before 2.3.4 and before 3.6.26. An attacker with CREATEDB privileges on a PostgreSQL server can craft a database name that allows execution of shell commands as the postgresql user when calling pglogical.create_subscription().

Patch / fix

fixed in 1 distros 1 links 1

2ndquadrant pglogical 2.3.4, 3.6.26

pglogical Debian 14, Debian 13, Debian 12 2.3.3-3

debian advisories DEBIAN-CVE-2021-3515

bugzilla.redhat.com/show_bug.cgi?id=1954112 advisory

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-3515 updated 2025-11-21 cvss 7.5

pglogical: Shell injection by pglogical users with CREATEDB access

Red Hat CloudForms Management Engine 5 rh-postgresql95-postgresql-pglogical
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
NVD	3.1	6.7	CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

n/a pglogical

Classification

Weakness

CWE-77 Improper Neutralization of Special Elements used in a Command
CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

bugzilla.redhat.com /show_bug.cgi?id=1954112
issue-tracking, patch, third-party-advisory

Sources

CVE List CVE-2021-3515
NVD CVE-2021-3515

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary