Skip to main content
Menu
CVEs

IBM Guardium Data Protection credential theft via TLS flaw in Terraform provider

CVE-2026-85018EUVD-2026-130728Published November 19, 2026, updated

8.1HighCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

IBM Guardium Data Protection has a flaw in the GDP Terraform provider, where TLS certificates are not properly validated. A network attacker positioned between the client and the Guardium appliance can intercept sensitive credentials sent to it, and this can be done remotely without logging in.

Written by a model

Original description

IBM Guardium Data Protection 12.2 is vulnerable to improper TLS certificate validation in the GDP Terraform provider, allowing a network attacker with a man-in-the-middle position to intercept sensitive credentials transmitted to the Guardium appliance.

Who should check

Teams running IBM Guardium Data Protection 12.2 that use the GDP Terraform provider to manage the appliance.

“IBM Guardium Data Protection 12.2”

ibm.com

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-85018 (IBM Guardium Data Protection Improper Certificate Validation), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-85018 (entry last updated 2026-11-20):
Affected:
- IBM Guardium Data Protection: versions 12.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Affects IBM Guardium Data Protection 12.2. (source: https://www.ibm.com/support/pages/node/7297484)
- Requires use of the GDP Terraform provider. (source: https://www.ibm.com/support/pages/node/7297484)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-85018 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-85018 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.ibm.com/support/pages/node/7297484
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-85018
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-85018"}.

Affected versions

cve.now Index

26Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.1/10CVSS 8.1, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 71 if added to CISA KEV
  • Would score about 66 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchibm.com · support/pages/node/7297484
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-85018
RecordNVD · CVE-2026-85018

Questions about CVE-2026-85018

Is CVE-2026-85018 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The GDP Terraform provider does not properly validate TLS certificates when it connects to a Guardium appliance. An attacker in a man-in-the-middle position on the network could intercept sensitive credentials sent to the appliance.

Source: ibm.com

Which versions are affected by CVE-2026-85018?

Guardium Data Protection: version 12.2.

Source: cve.now feed data

Am I affected, and how do I check?

The advisory states that IBM Guardium Data Protection 12.2 is affected, and the issue applies when the GDP Terraform provider is used. To check a setup, look at the Guardium version and whether the GDP Terraform provider is in use.

Source: ibm.com

How do I fix CVE-2026-85018?

No fixed version or vendor patch identifiers are listed in the checked facts, so check IBM's advisory for remediation details.

Source: ibm.com

No corrections so far. Something wrong on this page? Report an error.