CVE-2026-122043
Last modified
CVE-2026-122043 is a medium-severity vulnerability rated 6/10 on the CVSS scale. repmgr 4.0.0 through 5.5.0 is affected by an OS command injection vulnerability (CWE-78) in event notifications. When event_notification_command is configured, repmgr substitutes the %a (node name), %c (connection string) and %d (details) placeholders into the command and runs it through the shell. EPSS estimates a 1.04% chance of exploitation in the next 30 days.
Description
repmgr 4.0.0 through 5.5.0 is affected by an OS command injection vulnerability (CWE-78) in event notifications. When event_notification_command is configured, repmgr substitutes the %a (node name), %c (connection string) and %d (details) placeholders into the command and runs it through the shell. %a and %c are inserted without escaping, and %d escapes only double quotes, so shell command substitution still works inside the quoting the documentation recommends. The node name and connection string come from node records in the repmgr.nodes table. An attacker with the credentials of a non-superuser repmgr database user can write a crafted node record and run OS commands, as the operating system user that runs repmgr or repmgrd (usually postgres), on other cluster nodes that process an event using these placeholders. The %a placeholder of failover_validation_command has the same flaw. Deployments whose repmgr database user is a superuser gain no new capability, because a superuser can already run OS commands, and deployments that do not use these placeholders are not affected. The issue is fixed in repmgr 5.5.1. After upgrading, operators must remove any quotes they placed around these placeholders, because a placeholder left inside double quotes is still open to command injection.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| EnterpriseDB | repmgr | >= 4.0.0, < 5.5.1 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-122043?
How severe is CVE-2026-122043?
How do I fix CVE-2026-122043?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-12203A vulnerability was found in HKUDS AI-Trader up to 74caf996f…5.5
- CVE-2026-122032SPIP before 4.4.29 contains a SQL injection vulnerability th…6.5
- CVE-2026-122037The AgenWebsite Shipping – Plugin Ongkos Kirim & Generate Re…7.2
- CVE-2026-122038A vulnerability was identified in krupalshah EmployeeRecruit…7.3
- CVE-2026-12204A vulnerability was determined in ShopXO up to 6.7.1. This v…7.3
- CVE-2026-122041The Checkout Field Editor for WooCommerce (Pro) plugin for W…9.1
- CVE-2026-122044Philips Hue Bridge Pro Protection Mechanism Failure Authenti…8.8
- CVE-2026-122047A security vulnerability has been detected in Campcodes Comp…7.3
- CVE-2026-122048A vulnerability was identified in Campcodes Division Regiona…7.3
- CVE-2026-122049A flaw has been found in Campcodes Bitcoin Wallet System 1.0…3.7
- CVE-2026-12205Crypt::DSA versions before 1.21 for Perl reused the nonce ac…9.1
- CVE-2026-122050A vulnerability was found in Campcodes Complete Sales and In…7.3
Are you affected by CVE-2026-122043?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
