LiveActive security incident?Get immediate response
CVE Record

CVE-2026-35433: .NET Elevation of Privilege Vulnerability

Improper input validation in .NET allows an unauthorized attacker to elevate privileges locally.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

.NET has a local privilege elevation flaw caused by improper input validation. An attacker would need local access and user interaction, but successful exploitation could expose sensitive data, modify system state, and partially affect availability. Microsoft lists official remediation, so affected environments should patch on normal high-priority timelines.

Executive priority

Treat as a high-priority patching item, not an emergency internet-wide exposure based on current evidence. Focus first on systems where local users, developers, contractors, or automation can execute code.

Technical view

CVE-2026-35433 affects listed .NET 8.0, 9.0, 10.0, and .NET Framework configurations. The CVSS 3.1 score is 7.3 with local attack vector, low complexity, no privileges required, user interaction required, and high confidentiality and integrity impact. The CWE mapping includes integer overflow and improper input validation.

Likely exposure

Systems with the listed Microsoft .NET or .NET Framework versions installed are potentially exposed, especially workstations, application servers, build hosts, or shared systems where local code or user-launched content can interact with affected components.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. CVSS marks exploit code maturity as unproven. The attack is local and requires user interaction, limiting remote mass exploitation but still relevant for post-compromise privilege escalation.

Researcher notes

The bundle does not identify the vulnerable component, trigger condition, proof of concept, or precise user-interaction scenario. Avoid assuming exploitability beyond the CVSS and vendor description. Current analysis is limited to published CVE, MSRC, and Red Hat reference metadata.

Mitigation direction

  • Apply Microsoft updates referenced by the MSRC advisory.
  • Inventory installed .NET and .NET Framework versions across endpoints and servers.
  • Check Red Hat guidance for any Linux package applicability or non-affected status.
  • Prioritize shared systems, developer machines, build agents, and high-value application servers.
  • Use vendor guidance if patch details differ by operating system or package source.

Validation and detection

  • Confirm whether listed .NET or .NET Framework versions are present.
  • Verify Microsoft security updates are installed on affected Windows systems.
  • Review Red Hat CVE and VEX entries for applicable package status.
  • Document assets requiring delayed patching and compensating access controls.
  • Monitor vendor advisories for revised affected-version or remediation details.
Prepared
Confidence
medium
Sources
6

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 · low confidence lookup

CWE-190: 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 lookup
cwe · low confidence lookup

CWE-20: 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 lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35433 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
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L/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.

2CVSS vectors
5Timeline events
2ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

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
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L/E:U/RL:O/RC:C1.85.5microsoft
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L1.85.5redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L/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. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

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

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPdotnet: .NET: improper input validation allows an attacker to elevate privileges locally
other:Red Hat severity ratingcvssV3_1
  • 2026-05-12T18:01:11.848Z: Reported to Red Hat.
  • 2026-05-12T16:58:34.612Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Microsoft.NET 10.010.0.0Listed
Microsoft.NET 8.08.0.0Listed
Microsoft.NET 9.09.0.0Listed
MicrosoftMicrosoft .NET Framework 3.53.5.0Listed
MicrosoftMicrosoft .NET Framework 3.5 AND 4.7.24.7.0Listed
MicrosoftMicrosoft .NET Framework 3.5 AND 4.84.8.0Listed
MicrosoftMicrosoft .NET Framework 3.5 AND 4.8.14.8.1Listed
MicrosoftMicrosoft .NET Framework 4.84.8.0Listed
Weakness

CWE details

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.