Unauthenticated DoS via unsynchronized shared-map writes
Published Oct 8, 2026 · Updated Oct 8, 2026
A race condition in IBM Guardium Data Protection 12.2.2 allows remote attackers to interrupt service through concurrent shared-map writes. Concurrent writes are not synchronized; IBM does not identify the affected function or request path. No authentication or user interaction is required, but IBM does not specify whether the interruption is a crash or hang.
Summary
What happened
A race condition in IBM Guardium Data Protection 12.2.2 allows remote attackers to interrupt service through concurrent shared-map writes. Concurrent writes are not synchronized; IBM does not identify the affected function or request path. No authentication or user interaction is required, but IBM does not specify whether the interruption is a crash or hang.
The record
- CVE
- CVE-2026-84230
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Vendor
- IBM
- Product
- Guardium Data Protection
- Classifications
- CWE-362, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 8, 2026CVE publishedPublication date reported by the CVE source.
- Oct 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started