Security readout for executives and security teams
Plain-English summary
An authorized network user could exploit unsafe data handling in affected Microsoft SQL Server 2025 builds to run code on the database host. Successful exploitation could compromise sensitive data, alter systems, or disrupt service. The attacker needs some existing privileges, but no user interaction is required.
Executive priority
Treat as a high-priority remediation for affected, network-reachable database servers, especially those holding sensitive or operationally critical data. Prompt inventory and patch verification are warranted, but the supplied evidence does not justify an active-attack emergency designation.
Technical view
CVE-2026-54117 is a CWE-502 deserialization vulnerability with CVSS 3.1 score 8.8. It is network-accessible, low complexity, requires low privileges, and can cause high confidentiality, integrity, and availability impact. The supplied evidence does not identify the vulnerable protocol, deserialized object, or resulting execution context.
Likely exposure
Exposure is limited to the listed SQL Server 2025 builds: CU 6 version 17.0.4060.2 and x64 GDR version 17.0.1050.2. Practical risk requires network access and authorized low-privilege credentials. The bundle does not establish whether other releases are affected.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. Exploitation is nevertheless plausible because the vector indicates network access, low complexity, low privileges, and no user interaction. No public exploit availability is established by the supplied sources.
Researcher notes
The vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H with exploit maturity unproven and an official remedy indicated. Assessment should focus on trust boundaries, reachable authenticated roles, service execution privileges, and patch validation. Avoid assuming unauthenticated access or broader affected versions.
Mitigation direction
- Identify systems running either listed SQL Server 2025 build.
- Review Microsoft’s advisory and apply its approved security update.
- Restrict SQL Server network access to required systems and trusted users.
- Reduce unnecessary database accounts and privileges while remediation is pending.
Validation and detection
- Verify installed SQL Server edition and exact build against the affected list.
- Confirm the Microsoft security update completed successfully on every affected system.
- Recheck exposed network paths and low-privilege account access after remediation.
- Review relevant host and database telemetry for unexpected activity.
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 lookupExecution behavior lookup
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.
Open ATT&CK lookupCVE-2026-54117 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 SQL Server Remote Code Execution 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.