LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23659: Azure Data Factory Information Disclosure Vulnerability

Exposure of sensitive information to an unauthorized actor in Azure Data Factory allows an unauthorized attacker to disclose information over a network.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Microsoft lists CVE-2026-23659 as a high-severity Azure Data Factory information disclosure issue. The source says an unauthorized network attacker could disclose sensitive information. The business concern is exposure of confidential data in or reachable through Azure Data Factory workflows.

Executive priority

Treat this as a high-priority cloud data confidentiality risk. Prioritize verification and Microsoft-directed remediation for environments where Azure Data Factory handles sensitive, customer, or regulated data.

Technical view

The CVE is CWE-200 with CVSS 3.1 score 8.6: network reachable, low complexity, no privileges, no user interaction, changed scope, high confidentiality impact, no integrity or availability impact. Affected product detail is limited to Microsoft Azure Data Factory.

Likely exposure

Organizations using Azure Data Factory should assume potential exposure until they verify Microsoft guidance. The bundle does not identify specific versions, regions, configurations, tenants, pipelines, or integration runtime types.

Exploitation context

The bundle marks KEV as false and the CVSS vector lists exploit maturity as unproven. No supplied source states active exploitation or public exploit availability.

Researcher notes

Evidence is sparse beyond the CVE metadata and MSRC reference. Do not infer a vulnerable configuration or exploit path from the CVSS vector alone. Track MSRC for precise affected conditions and remediation mechanics.

Mitigation direction

  • Review the MSRC advisory for official remediation details.
  • Apply Microsoft-provided patches or service mitigations named by MSRC.
  • Inventory Azure Data Factory usage across all Azure tenants.
  • Prioritize workflows handling credentials, customer data, or regulated information.

Validation and detection

  • Confirm whether Azure Data Factory is deployed in each tenant.
  • Check MSRC for the current CVE status and remediation guidance.
  • Record affected subscriptions, data factories, and sensitive linked workflows.
  • Verify remediation evidence through Azure change records or vendor status.
Prepared
Confidence
medium
Sources
3

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-200: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23659 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

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.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C3.94microsoft

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2026-23659Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftAzure Data Factory-Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.