Keysight IxChariot Endpoint and associated products contain a stack-based buffer overflow. An unauthenticated remote attacker can send a specially crafted packet and execute arbitrary code with administrative privileges.
Security readout for executives and security teams
Plain-English summary
A network attacker could compromise vulnerable Keysight IxChariot Endpoint-related deployments without credentials or user interaction. Successful exploitation could provide administrative control, exposing data, altering systems, or disrupting service. The supplied version information is ambiguous, so organizations should verify affected releases directly against Keysight’s advisory.
Executive priority
Treat as an urgent remediation item because compromise requires neither credentials nor user action and may yield administrative control. Prioritize internet-accessible and broadly reachable deployments. Establish ownership immediately, verify scope with Keysight’s advisory, and track vendor-approved remediation to completion.
Technical view
CVE-2026-49435 is a stack-based buffer overflow (CWE-121) triggered by a specially crafted network packet. It is remotely reachable, requires no privileges or user interaction, and may enable arbitrary code execution with administrative privileges. CVSS 3.1 rates it 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Potential exposure includes IxChariot Endpoint and associated Hawkeye, IxChariot, IxTap, IxProbe, and IxByPass deployments. The bundle lists release numbers but does not clearly define affected ranges, and default status is unknown. Treat reachable installations as potentially exposed until Keysight guidance confirms otherwise.
Exploitation context
The bundle supports remote, unauthenticated code execution through a crafted packet. It does not provide exploit steps or establish exploitation in the wild. The CVE is not identified as being in CISA’s Known Exploited Vulnerabilities catalog.
Researcher notes
The supplied affected-version arrays are insufficiently explicit to infer reliable version ranges. Validate status through Keysight’s advisory and CISA CSAF data. No cited evidence establishes public exploitation, KEV inclusion, attack ports, packet format, or a specific fixed release; those details should not be assumed.
Mitigation direction
Consult Keysight’s security advisory to identify fixed or unaffected releases.
Inventory and prioritize all deployed IxChariot Endpoint-related products.
Restrict network access to affected components to trusted management and testing systems.
Apply vendor-provided updates or mitigations after confirming product and version applicability.
Validation and detection
Record installed product names, versions, and deployment locations.
Compare each deployment with the affected-status details in Keysight’s advisory.
Confirm vulnerable services are not reachable from untrusted networks.
Review security telemetry for unexpected administrative processes or suspicious traffic involving these systems.
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-121: 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.
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.
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
3Timeline events
1ADP providers
8Source links
SSVC decision data
cisa-cgCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-121 · source CWE mapping
Stack-based Buffer Overflow
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.