How severe is CVE-2026-80381?

CVE-2026-80381 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which products are affected by CVE-2026-80381?

CVE-2026-80381 affects the following products: ibm guardium data protection.

How do I patch CVE-2026-80381?

No patch has shipped for CVE-2026-80381 yet — track the ibm guardium data protection advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2026-80381 across my infrastructure?

Inventory every ibm guardium data protection deployment and check each version against the affected-products list above.

How do I mitigate CVE-2026-80381 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2026-80381 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-80381 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-80381?

CVE-2026-80381 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-80381?

CVE-2026-80381 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2026-80381?

CVE-2026-80381 affects ibm guardium data protection (6 versions, e.g. 12.0, 12.0.0, 12.1…). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2026-80381 published, and has it been updated?

CVE-2026-80381 was published on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

Not in CISA KEV

CRITICAL severity

CVE-2026-80381 — Guardium Data Protection

CRITICAL

CVE-2026-80381 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in ibm guardium data protection. No vendor fix is recorded yet; mitigation options are listed below.

IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements due to SQL injection.

Published

Oct 8, 2026

Updated

Oct 8, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-80381 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,993 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements due to SQL injection.

Affected Products

1 product · 6 configurations

Application

guardium data protectionibm

6 versions

12.012.0.012.112.1.012.212.2.0

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every ibm guardium data protection deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2026-80381 yet — track the ibm guardium data protection advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to execute unauthorized SQL statements due to SQL injection.

O3 Security · Runtime Protection

Is CVE-2026-80381 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2026-80381 — Guardium Data Protection

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2026-80381 being exploited in your environment?