CVE-2026-84272
validatedZero produced an exploit or a check.GHSA-9mjm-4wr5-3vgm ↗EUVD-2026-95239 ↗
description
IBM Guardium Data Protection 12.1 and 12.2.2 have an authentication weakness in the edge-controller. A remote party that can reach the component without credentials may cause container images to run and could take control of managed edge clusters.
mitigation
Restrict access to edge-controller endpoints to trusted management networks and monitor for unexpected container image execution. Apply an IBM-provided update when a fixed release is available.
outcome
Contextual check: a technique exists and was validated, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-08 19:05Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-84272
{ "etk_id": "ETK-2026-1000", "cve_id": "CVE-2026-84272", "display_id": "CVE-2026-84272", "ghsa_id": "GHSA-9mjm-4wr5-3vgm", "euvd_id": "EUVD-2026-95239", "status": "published", "anchor_state": "anchored", "title": "Missing authentication in Guardium Data Protection edge-controller", "summary": "IBM Guardium Data Protection 12.1 and 12.2.2 have an authentication weakness in the edge-controller. A remote party that can reach the component without credentials may cause container images to run and could take control of managed edge clusters.", "mitigation": "Restrict access to edge-controller endpoints to trusted management networks and monitor for unexpected container image execution. Apply an IBM-provided update when a fixed release is available.", "vendor": "IBM", "product": "Guardium Data Protection", "affected": [ { "affected_notes": [], "affected_ranges": [ "12.2.2", "12.1" ], "ecosystem": null, "fixed_versions": [], "package_name": "Guardium Data Protection", "purl": null } ], "cwes": [ 306 ], "cvss_score": 9.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "epss_score": 0.004, "epss_percentile": 0.3297, "epss_asof": "2026-10-20", "automation": "contextual", "check": true, "check_confidence_basis": "assessed", "exploit": false, "pipeline_minutes": 18.448515633333333, "t0_at": "2026-10-08T19:05:27.069000+00:00", "signals": { "check": { "at": "2026-10-08T22:17:41.252435+00:00", "days": 0.13349749346064815, "is_lower_bound": false, "measured_at": "2026-10-08T19:05:27.069000+00:00", "url": null }, "trigger_signal": { "at": "2026-10-08T19:05:27.069000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-08T19:05:27.069000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-84272" } } }
published 2026-10-08 19:39Z
last change 2026-10-21 05:31Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.