CVE-2026-81669: IBM Guardium Data Protection 12.2 is vulnerable to a command injection vulnerability in the create csr wildcar

This month

HIGH 7.2DOWNGRADE

CVE-2026-81669 is a high-severity flaw (CVSS 7.2) affecting guardium data protection. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

IBM Guardium Data Protection 12.2 is vulnerable to a command injection vulnerability in the create csr wildcard CLI command. An authenticated privileged CLI user can inject arbitrary shell commands through the alias input, resulting in command execution with root privileges.

Why this priority

High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	1.3% (top 29%)
CISA exploited list	No
Weakness	CWE-78
Published	2026-09-18
Last modified	2026-10-06

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-10-06 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-18 20:17 UTCPublished CVE record published
2026-10-06 14:13 UTCUpdated Record last modified

ibm guardium data protection DOWNGRADE

Affected: 12.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 12.2

1. Check installed version

apt-cache policy guardium-data-protection || rpm -q guardium-data-protection || guardium-data-protection --version

2. No fixed release: DOWNGRADE to a release before 12.2 (Debian / Ubuntu)

apt-cache madison guardium-data-protection sudo apt install guardium-data-protection=<VERSION_BEFORE_12.2> sudo apt-mark hold guardium-data-protection

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list guardium-data-protection sudo dnf downgrade guardium-data-protection-<VERSION_BEFORE_12.2> sudo dnf versionlock add guardium-data-protection

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-81669?

guardium data protection: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-81669 being exploited?

CVE-2026-81669 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-81669 affect?

CVE-2026-81669 affects guardium data protection. Severity is high (CVSS 7.2). IBM Guardium Data Protection 12.2 is vulnerable to a command injection vulnerability in the create csr wildcard CLI command. An authenticated privileged CLI user can inject arbitrary shell commands through the alias input, resulting in comm

How urgent is CVE-2026-81669?

Priority 43/100. High severity

Related CVEs

CVE-2026-1274 MEDIUM 4.9 DOWNGRADE IBM Guardium Data Protection 12.0, 12.1, and 12.2 is vulnerable to a Bypass Business Logic vulnerability in th
CVE-2026-4919 MEDIUM 4.8 DOWNGRADE IBM Guardium Data Protection 12.1 is vulnerable to cross-site scripting
CVE-2026-1272 LOW 2.7 DOWNGRADE IBM Guardium Data Protection 12.0, 12.1, and 12.2 is vulnerable to Security Misconfiguration vulnerability in
CVE-2026-8405 MEDIUM 6.5 DOWNGRADE IBM Guardium Data Protection 12.2.1, and 12.2.2 's add-on feature of Guardium Data Protection named "Long Term
CVE-2026-4918 MEDIUM 5.5 DOWNGRADE IBM Guardium Data Protection 12.1 is vulnerable to stored cross-site scripting

References

← Back to latest CVEs