Skip to main content

Guardium Data Protection EUVDEUVD-2026-95322

| CVE-2026-84891 HIGH
Use of Hard-coded Credentials (CWE-798)
2026-10-08 ibm GHSA-w2hj-jxpf-368j
7.5
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach Guardium service over network
  2. Exploit
    Supply hard-coded embedded credentials
  3. Execution
    Authenticate without prior privileges
  4. Impact
    Read sensitive information

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK

2 techniques across 2 tactics: Persistence, Credential Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that the attacker know or recover the hard-coded credentials embedded in IBM Guardium Data Protection (versions 12.0, 12.1, 12.2) and that the affected network service be reachable from the attacker's position; per CVSS PR:N/UI:N no legitimate account or user interaction is needed once the credentials are obtained. Limiting factors: the Guardium management/data service must be network-exposed to the attacker (typically a protected internal appliance rather than internet-facing), the attacker must first discover the static credentials, and impact is confined to disclosure of sensitive information (I:N/A:N) with no data modification or service disruption.

Impact

Signals are consistent and point to a genuine but moderate priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated flaw, which earns the 7.5 score entirely from a high confidentiality impact (C:H/I:N/A:N) with no integrity or availability effect. The CWE-798 (hard-coded credentials) classification aligns with this: an attacker who knows or recovers the embedded credentials can read sensitive data but cannot modify or disrupt the system per the scored impact. Real-world exploitation signals temper the raw score: EPSS is only 0.30% (21st percentile), there is no CISA KEV listing, and SSVC records Exploitation=none, Automatable=no, Technical Impact=partial. These lower-tier signals are coherent with each other and suggest this is not yet under active or automated exploitation. Note the SSVC 'partial' technical impact and the integrity/availability-free CVSS both reinforce that this is a disclosure-only issue rather than full compromise. No POC is referenced. Overall: a real, patch-worthy issue for exposed Guardium instances, but it is a high-CVSS/low-current-real-risk profile rather than an emergency - prioritize patching but it does not demand break-glass urgency absent exposure of the affected service to untrusted networks.

Exploit ScenarioDerived

A remote attacker who has obtained the hard-coded credentials (e.g., by extracting them from the product software or documentation) connects to a network-reachable Guardium Data Protection service and authenticates using those embedded credentials to retrieve sensitive information. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no prior privileges or user interaction are required once the credentials are known. No public exploit code is identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Oct 15, 2026

IBM Guardium Data Protection 12.0, 12.1, and 12.2 ship with hard-coded credentials that a remote, unauthenticated attacker (CVSS PR:N/UI:N) can abuse to read sensitive information from the affected appliance service, yielding a high confidentiality impact with no integrity or availability loss (C:H/I:N/A:N, base 7.5). Exploitation is not trivial in practice: the attacker must first know or recover the static credential value and must be able to reach the Guardium management or data service over the network, which is typically an internal, segmented appliance rather than an internet-facing endpoint. There is no confirmed active exploitation (not in CISA KEV), no public exploit code identified at time of analysis, and EPSS is only 0.30% (21st percentile), so this rates as a genuine but moderate-priority exposure that should be scheduled rather than emergency-patched.

Earlier versions of this analysis (1)
v1 Oct 08, 2026 - 22:07 CVSS 5.9

Hard-coded credentials in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can allow a remote attacker to obtain sensitive information once the embedded secret is extracted and the affected service is reachable. The assessed CVSS vector indicates no prior authentication or user interaction (PR:N/UI:N) and a confidentiality-only impact, with independent assessment rating this as moderate, non-urgent priority. No public exploit identified at time of analysis, and IBM has released a vendor patch.

RemediationAI

Patch available per vendor advisory: IBM documents the fix for CVE-2026-84891 at https://www.ibm.com/support/pages/node/7291675, and affected 12.0, 12.1, and 12.2 deployments should be updated to the release level specified there - no exact fix version is stated in the supplied data, so confirm the target build on that page before upgrading. Because hard-coded credentials cannot be rotated on unpatched systems, pre-patch compensating controls should focus on reachability and detection: restrict network access to the Guardium management and data-collection interfaces using firewall rules and segmentation so only trusted administration subnets can connect, accepting that this complicates distributed collector and aggregator topologies; place the appliances behind an authenticated jump host or VPN rather than exposing any service directly, with the trade-off of added operational friction for monitoring staff; and enable and forward audit logging for authentication events on the Guardium nodes to detect anomalous sessions that would indicate credential abuse, noting that logging alone will not prevent disclosure. IBM's advisory should be re-checked periodically for updated fix levels or additional hardening guidance, and because the flaw is product-wide, any newly deployed or restored 12.x instance should be brought to the patched level before being attached to the network.

Affected VersionsENISA

Guardium Data Protection 12.0
Guardium Data Protection 12.1
Guardium Data Protection 12.2

Affected Packages

euvd guardium_data_protection no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-798, Use of Hard-coded Credentials: authentication secrets are embedded in the IBM Guardium Data Protection product (versions 12.0, 12.1, 12.2) rather than being generated per installation or stored in a protected credential store. Because the same static value is baked into the software, anyone who extracts it from shipped binaries, configuration artifacts, documentation, or another deployment can authenticate to the affected service without needing a valid account. The CPE string cpe:2.3:a:ibm:guardium_data_protection:*:*:*:*:*:*:*:* confirms a product-wide (all-version) matching entry, and ENISA EUVD-2026-95322 independently lists the same three affected release lines. Guardium is a database activity monitoring and data-protection platform, so the sensitive information reachable through an authenticated session can include monitored database traffic metadata, audit records, and configuration data - which is why the vector assigns confidentiality:high. The network attack vector with no privileges or user interaction required reflects that the flaw is exploitable purely over the network once the credential is known; the static, product-wide nature of the secret is what transforms a normally authenticated interface into an unauthenticated one.

Know when Guardium Data Protection gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ibm) PRIMARY MEDIUM
NVD 7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 7.5 HIGH

Hard-coded credentials are usable over the network with no attacker-side privileges (PR:N) or interaction, yielding confidentiality-only impact so I:N/A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Severity Changed
Oct 15, 2026 - 17:07 NVD
MEDIUM HIGH
CVSS changed
Oct 15, 2026 - 17:07 NVD
5.9 (MEDIUM) 7.5 (HIGH)

DescriptionNVD

IBM Guardium Data Protection 12.0, 12.1, and 12.2 could allow a remote attacker to obtain sensitive information due to use of hard-coded credentials.

Executive ViewAI

Why It Matters

IBM Guardium Data Protection versions 12.0, 12.1, and 12.2 are affected by a high-severity vulnerability involving hard-coded credentials that could allow a remote, unauthenticated attacker to read sensitive information from the appliance. Although no public exploit identified at time of analysis and exploitation requires knowledge of the static credential and network access to typically segmented internal systems, a successful breach could expose sensitive data and undermine confidence in the organization's data protection controls. Leadership should prioritize patching this critical security infrastructure to prevent potential data exposure.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Medium
specialized enterprise data-security appliance, common in large orgs not everywhere
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Partial

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2026-84064 CRITICAL
9.9 Sep 18

SQL injection in IBM Guardium Data Protection 12.2 allows a remote authenticated attacker to execute arbitrary SQL comma

CVE-2026-84075 CRITICAL
9.9 Sep 18

Unauthenticated remote attackers can bypass security restrictions in IBM Guardium Data Protection 12.2 through the Chang

CVE-2026-84078 CRITICAL
9.9 Sep 18

Missing authentication in the LoadBalancerServlet of IBM Guardium Data Protection 12.2 allows unauthenticated, network-r

CVE-2026-81657 CRITICAL
9.8 Sep 18

Unauthenticated remote code execution in IBM Guardium Data Protection 12.2 lets a network attacker who can reach the app

CVE-2026-75875 CRITICAL
9.8 Oct 08

Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers

CVE-2026-82340 CRITICAL
9.8 Sep 18

Unauthenticated insecure deserialization in the Change Audit System (CAS) listener of IBM Guardium Data Protection 12.2

CVE-2026-82967 CRITICAL
9.8 Sep 18

Authentication bypass in IBM Guardium Data Protection 12.2 lets an unauthenticated remote attacker evade the IP-based ac

CVE-2026-84249 CRITICAL
9.8 Oct 08

Missing authentication on a critical management function in IBM Guardium Data Protection 12.2 and 12.2.2 allows unauthen

CVE-2026-84272 CRITICAL
9.8 Oct 08

Missing authentication in the edge-controller component of IBM Guardium Data Protection 12.1 and 12.2.2 allows unauthent

CVE-2026-84082 CRITICAL
9.8 Sep 18

Unauthenticated SQL injection in IBM Guardium Data Protection 12.2 lets a remote attacker submit crafted input that is c

CVE-2026-82344 CRITICAL
9.8 Oct 08

A heap-based buffer overflow in IBM Guardium Data Protection's S-TAP TrafficTap TDS login reassembly routine allows an u

CVE-2026-80441 CRITICAL
9.8 Sep 18

Second-order SQL injection in IBM Guardium Data Protection 12.2 allows an unauthenticated remote attacker to submit SQL

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy