CVE-2026-50775: A blind SSRF attack in DataHub v.1.5.0.1 allows a remote attacker to execute arbitrary code via the server...
A blind SSRF attack in DataHub v.1.5.0.1 allows a remote attacker to execute arbitrary code via the server retrieving an image from a crafted URL, and it fails to return the content or any errors directly.
Security readout for executives and security teams
Plain-English summary
The cited CVE record describes a critical flaw in DataHub v1.5.0.1. An unauthenticated attacker could supply a crafted image URL, causing the server to contact unintended systems and potentially execute arbitrary code. Because the request is blind, attacks may not produce visible responses or errors.
Executive priority
Treat confirmed matching deployments as urgent because the cited impact includes full confidentiality, integrity, and availability loss without authentication. Prioritize exposure confirmation and temporary egress restrictions immediately. Do not claim remediation is complete until official vendor guidance identifies a fix or supported mitigation.
Technical view
The issue is classified as CWE-918 blind server-side request forgery in server-side image retrieval. The supplied CVSS 3.1 score is 9.8, with network access, low complexity, no privileges, and no user interaction. The cited description claims a path to arbitrary code execution, but does not document the chain in detail.
Likely exposure
Potential exposure is limited to deployments matching DataHub v1.5.0.1 that permit attacker-controlled image URLs. The supplied structured affected-product fields are unspecified, so product identity and version scope require confirmation before making inventory-wide conclusions.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not identified as being in KEV. A public researcher repository is referenced, but its existence alone does not prove real-world attacks. Blind behavior could make exploitation harder to observe.
Researcher notes
Evidence is incomplete. The narrative names DataHub v1.5.0.1, while structured affected vendor and product fields are “n/a.” The supplied sources do not identify a patch, affected configuration boundaries, technical RCE chain, or observed exploitation. Validate attribution and scope independently.
Mitigation direction
Identify deployments matching the named product and version before prioritizing remediation.
Check DataHub and CVE guidance for an official fixed version or mitigation.
Disable unneeded server-side image retrieval from user-controlled URLs.
Restrict application egress to approved destinations and block private, loopback, and link-local ranges.
Monitor image-retrieval traffic for unexpected internal or external destinations.
Validation and detection
Confirm the deployed product identity and exact version from authoritative inventory records.
Determine whether untrusted users can submit URLs used for server-side image retrieval.
Review outbound network controls covering the affected service.
Inspect application, proxy, DNS, and firewall logs for unusual image-fetch destinations.
Verify vendor guidance before declaring the deployment patched or unaffected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-918 · source CWE mapping
Server-Side Request Forgery
Server-Side Request Forgery represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.