Security readout for executives and security teams
Plain-English summary
This issue affects the 2025 Indian Motorcycle Scout Bobber + Tech. A person with physical access to specific WCM wiring could prevent the anti-theft shutdown from taking effect, allowing the motorcycle to remain operable without PIN validation. The source indicates connector details are withheld pending vendor remediation.
Executive priority
Treat as a moderate physical theft-control weakness. Prioritize dealer or vendor confirmation for affected assets, especially fleets or high-theft-risk environments. There is no sourced evidence of remote exploitation or active exploitation.
Technical view
The shutdown signal uses a falling-edge voltage transition between the Wireless Control Module and a peer ECU. The receiving ECU reportedly does not distinguish a valid shutdown pulse from an open-circuit or disconnected condition. The CVSS score is 4.6, physical attack vector, low complexity, no privileges or user interaction, with high availability impact.
Likely exposure
Exposure appears limited to physical attackers who can access the relevant WCM wiring harness on the 2025 Scout Bobber + Tech. The source bundle names no other affected models or years.
Exploitation context
No active exploitation is reported in the provided sources, and the CVE is not marked KEV. The scenario is physical tampering, not remote compromise. Specific connector details were intentionally withheld pending remediation.
Researcher notes
Evidence is limited to the CVE description and CWE reference. Do not assume other Indian Motorcycle models are affected. The public record withholds connector details, so validation should remain non-destructive and vendor-coordinated.
Mitigation direction
- Check Indian Motorcycle guidance for service actions, recalls, or firmware/hardware remedies.
- Restrict unattended physical access to affected motorcycles where practical.
- Inspect WCM-area wiring for tampering during service or theft investigations.
- Document affected inventory by model and year.
Validation and detection
- Confirm whether the motorcycle is a 2025 Scout Bobber + Tech.
- Review service records for WCM or ECU remediation notices.
- Ask the vendor or dealer for CVE-specific remediation status.
- Inspect relevant wiring areas for signs of unauthorized access.
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-1384: 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-693: 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-754: 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-49325 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
- Medium
- CVSS
- 4.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H0.93.6ASRGCVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N——ASRGVulnerability scoring details
Base CVSS 4.0 score
4.1MediumVector: CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Base CVSS 3.1 score
4.6MediumVector: CVSS:3.1/AV:P/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.
- Source timelineASRG
Reported to Indian Motorcycle by Rustic Security LLC (responsible disclosure)
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://cwe.mitre.org/data/definitions/1384.htmlCVE reference, ASRG · technical-description
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.
Improper Handling of Physical or Environmental Conditions
Improper Handling of Physical or Environmental Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.