Security readout for executives and security teams
Plain-English summary
This issue can let someone with access to the motorcycle’s in-vehicle network intentionally lock the immobilizer, leaving a 2025 Indian Scout Bobber + Tech unable to start until dealer service. It is not described as remotely exploitable over the internet.
Executive priority
Treat as a targeted disruption risk, not a broad remote compromise. Prioritize affected high-value, fleet, or customer-facing bikes, especially where many people have physical or service access.
Technical view
The WCM brute-force lockout counter can be advanced by unauthenticated messages, is not session-bound, and persists across power cycles. The result is a denial-of-service condition affecting availability. The CVE maps to CWE-307, CWE-400, and CWE-770 with CVSS 4.6.
Likely exposure
Exposure appears limited to 2025 Indian Motorcycle Scout Bobber + Tech models where an attacker can gain write access to the in-vehicle network. Owners, dealers, rental fleets, and service environments should consider physical and diagnostic access controls.
Exploitation context
The source bundle does not indicate active exploitation, and CISA KEV status is false. Specific lockout thresholds were withheld pending remediation. Practical exploitation requires close or physical access to vehicle communications, but impact is disruptive once access exists.
Researcher notes
Evidence supports an immobilizer denial-of-service via unauthenticated WCM lockout counter manipulation. Do not publish thresholds or reproduce lockouts on live vehicles. Vendor remediation details are not provided in the source bundle.
Mitigation direction
- Check Indian Motorcycle and dealer advisories for WCM remediation or service instructions.
- Restrict physical and diagnostic access to affected motorcycles.
- Avoid leaving affected vehicles unattended in untrusted service or storage environments.
- Document affected VINs and WCM software status through authorized service channels.
- Do not attempt lockout testing on operational motorcycles.
Validation and detection
- Inventory 2025 Scout Bobber + Tech motorcycles in ownership or service.
- Confirm WCM status and available updates with an authorized dealer.
- Review who can access diagnostic ports or in-vehicle network interfaces.
- Track CVE and ASRG advisory updates for remediation details.
- Verify recovery procedures before any security assessment.
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-307: 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-400: 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-770: 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-49324 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://www.asrg.io/security-advisories/cve-2026-49324-indian-scout-wcm-bruteforce-lockout-dosCVE reference, ASRG · third-party-advisory
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 Restriction of Excessive Authentication Attempts
Improper Restriction of Excessive Authentication Attempts represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Uncontrolled Resource Consumption
Uncontrolled Resource Consumption represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.