CVE-2026-49323: Indian Scout Bobber 2025 WCM-to-ECM weak authentication
Weak authentication between the Wireless Control Module (WCM) and the Engine Control Module (ECM) of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker with read access to the in-vehicle network to recover the per-vehicle ECM immobilizer secret by passively observing a single seed/key exchange. The WCM derives its response using a reversible, non-cryptographic operation rather than a cryptographic challenge-response, so the persistent immobilizer secret can be reconstructed from one captured exchange. With this secret the attacker can authenticate to the ECM independently of the WCM and start the engine, defeating the immobilizer. Specific protocol details have been withheld pending vendor remediation.
Security readout for executives and security teams
Plain-English summary
This issue affects the 2025 Indian Motorcycle Scout Bobber + Tech. A nearby attacker with access to the motorcycle’s in-vehicle network could observe one authentication exchange and recover a persistent immobilizer secret. That secret could let them authenticate to the engine controller and start the engine, bypassing the immobilizer.
Executive priority
Treat as a targeted theft-risk issue, not a broad network emergency. Prioritize fleets, dealers, rentals, and high-value exposed inventory. The key decision is whether affected motorcycles can receive vendor remediation or need interim physical security controls.
Technical view
The WCM-to-ECM authentication uses a reversible, non-cryptographic seed/key mechanism. Passive observation of a single exchange can reconstruct the per-vehicle ECM immobilizer secret. CVSS 3.1 is 4.3, with physical attack vector, low complexity, no privileges, user interaction required, and high confidentiality impact. Protocol details are intentionally withheld pending remediation.
Likely exposure
Exposure appears limited to Indian Motorcycle Scout Bobber + Tech model year 2025. The attacker needs proximity and read access to the in-vehicle network, so this is not an internet-scale vulnerability. Business impact is theft and immobilizer bypass risk for affected motorcycles.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not listed as KEV. Exploitation requires adjacent or physical context, observation of one WCM-to-ECM exchange, and later use of the recovered immobilizer secret. Public protocol details are withheld.
Researcher notes
The advisory identifies CWE-1390, CWE-327, and CWE-798 themes: weak authentication, broken cryptographic design, and recoverable persistent secrets. Do not assume additional Indian Motorcycle models are affected; the provided data names only Scout Bobber + Tech 2025. Evidence on patch availability is incomplete.
Mitigation direction
Check Indian Motorcycle or dealer guidance for an official remediation or service bulletin.
Limit unauthorized physical access to affected motorcycles and diagnostic or in-vehicle network interfaces.
Use layered anti-theft controls until vendor remediation is confirmed.
Track ASRG advisory updates for vendor remediation status.
Validation and detection
Confirm whether assets are Indian Motorcycle Scout Bobber + Tech model year 2025.
Review vendor or dealer records for applicable firmware, service, or recall updates.
Assess physical access controls around stored or serviced affected motorcycles.
Monitor CVE and ASRG pages for updated affected-version and remediation details.
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-1390: 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.
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.
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 authentication or credential exposure, so valid-account and credential-access review may help. 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.
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-1390 · source CWE mapping
Weak Authentication
Weak Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.