Security readout for executives and security teams
Plain-English summary
CVE-2026-23666 is a remotely reachable denial-of-service flaw in affected Microsoft .NET Framework versions. An unauthenticated attacker could disrupt applications or services that process malicious network input. The supplied severity is high because exploitation requires low complexity and no user action, although the reported impact is limited to availability rather than data theft or modification.
Executive priority
Prioritize prompt remediation for exposed or operationally critical services. The issue can interrupt availability without credentials or user interaction, but the sources do not indicate data compromise or active exploitation. Treat internet-facing workloads as the first deployment group and manage updates through normal change controls.
Technical view
Improper input validation can cause denial of service over a network. The CVSS 3.1 score is 7.5: network-accessible, low complexity, unauthenticated, and requiring no user interaction, with high availability impact but no stated confidentiality or integrity impact. The record associates the issue with CWE-366 and CWE-755.
Likely exposure
Potentially exposed systems include network-facing applications or services running the listed .NET Framework 3.5, 4.6.2–4.7.2, 4.8, or 4.8.1 configurations. The bundle does not identify specific application features or vulnerable input paths, so installed runtime versions and application reachability require local verification.
Exploitation context
The CVSS vector reports proof-of-concept exploit maturity, but the supplied bundle provides no exploit details. The CVE is not listed in CISA KEV, and no cited evidence establishes active exploitation. Successful attacks are described as affecting service availability only.
Researcher notes
The public bundle gives no vulnerable component, triggering input format, crash mechanism, or affected code-path detail. Product naming includes combined framework configurations, so avoid inferring broader version coverage. Validate applicability against Microsoft’s advisory and installed Windows/.NET servicing state. Proof-of-concept maturity is reported only through the supplied CVSS vector.
Mitigation direction
- Review Microsoft’s CVE advisory and apply the applicable vendor security update.
- Prioritize internet-facing or business-critical services using affected .NET Framework versions.
- Restrict unnecessary network access to affected applications until updates are completed.
- Use service monitoring and recovery controls to reduce denial-of-service impact.
Validation and detection
- Inventory installed .NET Framework versions across supported Windows systems.
- Map affected runtimes to network-reachable applications and critical services.
- Confirm the applicable Microsoft security update is installed successfully.
- Monitor affected services for crashes, hangs, or unusual availability degradation.
- Recheck Microsoft guidance for product-specific prerequisites or superseding updates.
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-366: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-755: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-23666 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
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/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
2 official scoresWe 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:U/C:N/I:N/A:H/E:P/RL:O/RC:C3.93.6microsoftCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-14T18:01:54.434Z: Reported to Red Hat.
- 2026-04-14T16:57:53.069Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- .NET Framework Denial of Service VulnerabilityCVE reference, microsoft · vendor-advisory, patch
- https://access.redhat.com/security/cve/CVE-2026-23666CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2458271CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23666.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
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.
Race Condition within a Thread
Race Condition within a Thread represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.