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

A local attacker could abuse improper input handling in affected Microsoft .NET installations to gain higher privileges. Successful exploitation requires user interaction but no prior privileges, and could significantly compromise confidentiality and integrity while causing limited availability impact.

Executive priority

Treat as a high-priority patching issue, especially for shared endpoints and systems exposed to untrusted users. It is not evidenced as an emergency internet-scale threat because exploitation is local, requires user interaction, and active exploitation is not established.

Technical view

CVE-2026-35433 is a local elevation-of-privilege flaw involving improper input validation and integer handling (CWE-20 and CWE-190). It carries CVSS 3.1 score 7.3: local access, low complexity, no privileges, user interaction required, unchanged scope, and high confidentiality and integrity impact.

Likely exposure

Exposure applies where the specifically listed .NET 8.0, 9.0, 10.0 or .NET Framework variants are installed. Risk is more relevant on endpoints, shared systems, and servers where an attacker can obtain local access or induce an authorized user to interact.

Exploitation context

The supplied record does not establish active exploitation, and the CVE is not identified as being in CISA KEV. The vector indicates exploitation is local, requires user interaction, needs no prior privileges, and has low attack complexity. Public exploit availability is not established by the supplied sources.

Researcher notes

The public bundle identifies input validation and integer-handling weaknesses but provides insufficient detail to determine the vulnerable component, trigger, or exact privilege boundary. Affected-product entries include combined Framework labels and should be reconciled with Microsoft’s advisory. No exploit procedure, fixed-build matrix, or active exploitation evidence is supplied.

Mitigation direction

  • Review the Microsoft advisory and apply its applicable security updates promptly.
  • Prioritize affected shared systems and endpoints permitting untrusted local access.
  • Restrict unnecessary local and interactive access while remediation is pending.
  • Follow vendor guidance for supported update paths; fixed build details are absent from the bundle.

Validation and detection

  • Inventory installed .NET runtimes and Framework versions against the affected product list.
  • Confirm applicable Microsoft security updates are installed using approved endpoint-management records.
  • Re-scan remediated systems and investigate installations that remain on affected versions.
  • Verify critical applications still operate correctly after updating .NET components.
Prepared
Confidence
medium
Sources
4

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.