Security readout for executives and security teams
Plain-English summary
A critical flaw in Microsoft Planetary Computer Pro (GeoCatalog) may let an unauthenticated remote attacker expose information by sending untrusted serialized data. The supplied CVSS score is 10.0, indicating potentially severe business impact. The source bundle does not identify affected versions, so any GeoCatalog deployment should be treated as potentially exposed until Microsoft guidance confirms otherwise.
Executive priority
Treat this as an immediate validation and remediation priority for organizations using GeoCatalog. Assign ownership, establish deployment scope, and confirm Microsoft’s remediation status quickly. Systems with external or broad network exposure should be addressed first. Organizations without Planetary Computer Pro GeoCatalog have no indicated exposure from the supplied evidence.
Technical view
CVE-2026-41104 is a CWE-502 deserialization vulnerability reachable over the network without privileges or user interaction. Its CVSS 3.1 vector reports low complexity, changed scope, and high confidentiality, integrity, and availability impacts. However, the supplied description specifically confirms information disclosure; further impact details and affected versions are not provided.
Likely exposure
Exposure is most likely where Microsoft Planetary Computer Pro GeoCatalog is deployed and network-accessible. The affected-version field is unspecified, preventing reliable version-based scoping. Organizations should inventory all instances, including externally reachable and partner-accessible deployments, then compare their service status with Microsoft’s advisory.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. It also provides no public exploit evidence. Nevertheless, network reachability, no authentication, no user interaction, low complexity, and a 10.0 CVSS score make prompt defensive action appropriate. Absence from KEV does not prove exploitation is impossible.
Researcher notes
The evidence establishes CWE-502 and a critical remote, unauthenticated attack surface, but omits affected versions, vulnerable components, technical prerequisites, and observed indicators. The CVSS vector claims high integrity and availability impact despite an information-disclosure title and description. Researchers should preserve this distinction and rely on Microsoft for confirmed scope and remediation details.
Mitigation direction
- Review Microsoft’s CVE advisory for the applicable update or service-side remediation.
- Apply Microsoft’s supported remediation to every affected GeoCatalog deployment promptly.
- Restrict GeoCatalog network access to trusted users and systems while remediation is pending.
- Monitor vendor guidance because affected versions are not specified in the supplied sources.
Validation and detection
- Inventory all Microsoft Planetary Computer Pro GeoCatalog deployments and owners.
- Identify internet-facing, partner-accessible, and broadly reachable GeoCatalog endpoints.
- Compare each deployment’s version and update status against Microsoft’s advisory.
- Review logs for unusual unauthenticated requests or unexpected information exposure.
- Confirm remediation through configuration records and Microsoft-supported version evidence.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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 lookupCVE-2026-41104 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C3.96microsoftVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Planetary Computer Pro Information Disclosure VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.