Skip to main content

Scout Bobber Tech EUVDEUVD-2026-33293

| CVE-2026-49316 MEDIUM
Expected Behavior Violation (CWE-440)
2026-05-29 ASRG GHSA-xpm6-xp6j-7w29
4.1
CVSS 4.0 · Vendor: ASRG
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Achieve adjacent proximity to target motorcycle
  2. Delivery
    Access CAN bus via OBD-II or WCM wireless
  3. Exploit
    Inject timed error frames targeting WCM broadcasts
  4. Install
    Drive WCM transmit error counter to bus-off
  5. C2
    WCM silenced - immobilizer command ceases
  6. Execute
    Peer ECUs continue operation without lockout
  7. Impact
    Start and operate motorcycle undetected

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Expected behavior violation
Exploitation Conditions

The attacker must be within physical proximity to the motorcycle sufficient to reach the OBD-II port or the WCM's wireless interface - the exact required distance is unconfirmed due to a conflict between the CVE description's 'adjacent-network' characterization and the CVSS AV:P vector (see risk assessment). The WCM must be in its normal active state, periodically broadcasting immobilizer-state messages on the CAN bus; this is the default condition for any parked or running 2025 Scout Bobber + Tech with the anti-theft system engaged, requiring no non-default configuration. No authentication, credentials, or victim interaction are required (PR:N, UI:N). AT:P (Attack Requirements: Present) reflects the specific precondition that the attacker must be able to time CAN error frames to collide with WCM transmissions, requiring either direct bus wiring access or a compatible wireless CAN injection capability. Exploitation is limited by the need for proximity sufficient to sustain the injection, the requirement for CAN-capable hardware and tooling, the absence of publicly disclosed protocol specifics, and the fact that ASRG has withheld full technical details. The vulnerability does not apply to Indian Motorcycle models that do not use the WCM-based anti-theft architecture or to model years other than 2025 as currently scoped.

Impact

The CVSS 4.0 base score of 4.1 (Medium) is driven by AV:P (Physical attack vector), which bounds exploitation to actors within direct or adjacent range of the vehicle, and AT:P (Attack Requirements: Present), indicating the WCM must be actively transmitting - its normal operating state - for the attack to proceed. PR:N and UI:N confirm no credentials or victim interaction are needed once proximity is established. VA:H captures the WCM being forced bus-off. A notable analytical tension exists: the CVE description characterizes the threat actor as 'an adjacent-network attacker,' which in CVSS 4.0 terminology implies AV:A, yet the submitted vector specifies AV:P. This discrepancy is material - AV:A would allow exploitation from several meters via the WCM's wireless interface without physical contact, while AV:P requires direct bus access; defenders cannot make precise access-control decisions until this is clarified by ASRG or the vendor. The subsequent-system impact metrics (SC/SI/SA) are all rated None, which technically understates the real-world consequence: the motorcycle becomes stealable. No EPSS data was provided. No CISA KEV listing exists, indicating no confirmed widespread active exploitation. The underlying bus-off injection technique is described by ASRG as 'well-known' in automotive security research, but no public exploit tool targeting this specific vehicle has been identified, and full protocol specifics are withheld.

Exploit ScenarioDerived

An attacker carrying a commodity USB-to-CAN adapter and a laptop approaches a parked 2025 Scout Bobber + Tech in a public space, accesses the CAN bus via the OBD-II diagnostic port or via the WCM wireless interface, and transmits malformed CAN error frames timed to collide with the WCM's periodic immobilizer-state broadcasts. Within seconds to minutes, the WCM's transmit error counter reaches 255 and the module enters bus-off, permanently silencing its shutdown command for the remainder of the power cycle. With no ECU issuing a lockout, the attacker starts the engine using the ignition switch and rides away; no public exploit tool exists for this specific vehicle, but the bus-off injection technique itself is documented in automotive security research literature.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 29, 2026

CAN bus error-frame injection on the 2025 Indian Motorcycle Scout Bobber + Tech defeats the Wireless Control Module (WCM)-enforced immobilizer, enabling vehicle operation without legitimate anti-theft deactivation. An attacker within physical or adjacent proximity drives the WCM's CAN controller into bus-off state by incrementing its transmit error counter past the threshold, permanently silencing the WCM's periodic shutdown command. Because peer ECUs treat WCM silence as benign rather than a security event - a fail-open design - the motorcycle becomes fully operable as though the immobilizer were properly unlocked. No public exploit code has been identified at time of analysis; ASRG is withholding full protocol details pending vendor remediation, reported under CVE-2026-49316.

RemediationAI

No vendor-released patch has been identified at time of analysis. ASRG has disclosed the vulnerability under coordinated conditions and is withholding full technical protocol details pending remediation by Indian Motorcycle / Polaris Inc.; owners and fleet operators should monitor Polaris Inc. official security channels for a WCM firmware update that redefines bus-off handling - the durable fix requires peer ECUs to treat WCM silence as a security-relevant event and assert an independent immobilizer lockout. Until a firmware update is available, the following specific compensating controls reduce risk with noted trade-offs: physically securing the OBD-II port (aftermarket port locks, tamper-evident covers) raises the bar for wired CAN injection - trade-off: does not address a wireless CAN injection path if the attacker exploits the WCM wireless interface. Storing the motorcycle in a locked, monitored enclosure limits attacker dwell time required to complete the error-counter increment sequence - trade-off: logistically impractical for daily riders. Installing an aftermarket GPS tracker provides theft detection rather than prevention, enabling rapid recovery - trade-off: does not prevent the bypass. None of these measures address the fail-open WCM silence design; only an OEM-supplied firmware update constitutes a structural fix.

Affected VersionsENISA

Scout Bobber + Tech 2025

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The 2025 Indian Motorcycle Scout Bobber + Tech (Polaris Inc.) uses a Controller Area Network (CAN) bus for intra-vehicle ECU communication per ISO 11898. The Wireless Control Module (WCM) is the anti-theft enforcement node, periodically broadcasting an immobilizer-state message that keeps the shutdown engaged unless a legitimately authenticated key-fob transaction releases it. CAN is a multi-master bus with no native message authentication; its error confinement mechanism is engineered for fault tolerance, not adversarial resilience. ISO 11898 error confinement defines a transmit error counter (TEC) that increments on detected transmission faults; at TEC=255 the node enters bus-off state and ceases all CAN activity. CWE-440 (Expected Behavior Violation) is the root cause: the WCM's bus-off silence is an expected hardware behavior from a fault-tolerance perspective, but the peer ECUs violate the security expectation by not treating that silence as an immobilizer-relevant event - producing a fail-open outcome. CPE cpe:2.3:a:indian_motorcycle_(polaris_inc.):scout_bobber_+_tech:*:*:*:*:*:*:*:* with a wildcard version segment indicates all known firmware revisions of the 2025 model year are in scope.

Know when Scout Bobber Tech gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (ASRG) PRIMARY 4.1 MEDIUM
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

Primary rating from Vendor (ASRG) · only source for this CVE.

CVSS VectorVendor: ASRG

Attack Vector
Physical
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
None
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

1
CVSS changed
May 29, 2026 - 14:22 NVD
4.6 (MEDIUM) 4.1 (MEDIUM)

DescriptionCVE.org

Expected behavior violation in the in-vehicle network of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker to bypass the motorcycle's anti-theft shutdown by forcing the Wireless Control Module (WCM) into the CAN bus-off state. Using a well-known CAN error-frame injection technique against a periodic WCM transmission, the attacker drives the WCM CAN controller's transmit error counter past the bus-off threshold, after which the WCM stops transmitting all messages, including the shutdown command. Peer ECUs do not interpret WCM silence as a security event and continue normal operation, allowing the motorcycle to be operated despite the immobilizer never having been unlocked. Specific protocol details have been withheld pending vendor remediation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

20
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +20
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy