cve.bz

CVE-2026-66800 microsoft azure data factory: SSRF

7.5 highEPSS 1.0%

High (7.5) in microsoft azure data factory. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
Server-side request forgery (ssrf) in Azure Data Factory allows an unauthorized attacker to disclose information over a network.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 63rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-66800 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-66800?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-66800?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-66800 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Azure Data Factory-

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important. A namespace administrator within the `open-cluster-management-backup` namespace in Red Hat Advanced Cluster Management for Kubernetes can initiate a cluster-wide denial of service. This occurs by leveraging the `cleanupBeforeRestore: CleanupAll` option in a Restore Custom Resource, which causes the `cluster-backup-operator` to delete all ACM/Hive-labelled Secrets and ConfigMaps across the hub cluster, regardless of their restore labels.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Advanced Cluster Management for Kubernetes 2.11rhacm2/cluster-backup-rhel9-operator:1787684668Fixed 2026-08-26RHSA-2026:60387
Red Hat Advanced Cluster Management for Kubernetes 2.13rhacm2/cluster-backup-rhel9-operator:1787259060Fixed 2026-08-26RHSA-2026:60390
Red Hat Advanced Cluster Management for Kubernetes 2.14rhacm2/cluster-backup-rhel9-operator:1787183178Fixed 2026-08-26RHSA-2026:60388
Red Hat Advanced Cluster Management for Kubernetes 2.15rhacm2/cluster-backup-rhel9-operator:1787238500Fixed 2026-08-26RHSA-2026:60389
Red Hat Advanced Cluster Management for Kubernetes 2.16rhacm2/cluster-backup-rhel9-operator:1787183176Fixed 2026-08-26RHSA-2026:60391
Red Hat Advanced Cluster Management for Kubernetes 2.17rhacm2/cluster-backup-rhel9-operator:1787227576Fixed 2026-08-26RHSA-2026:60386

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-66800.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON