Security readout for executives and security teams
Plain-English summary
On the 2025 Indian Motorcycle Scout Bobber + Tech, the Infotainment Digital Round display can skip the PIN screen if Wireless Control Module traffic is absent during boot. This may show the normal interface without PIN entry. The CVE rates this low severity because the stated impact is limited confidentiality exposure and requires close/physical or adjacent access.
Executive priority
Treat as low urgency but worth tracking for affected fleets. Business impact is likely privacy or user-interface exposure, not confirmed vehicle control. Prioritize vendor confirmation during normal maintenance unless affected motorcycles handle sensitive rider data or face elevated tampering risk.
Technical view
The display uses WCM traffic during a boot window as a proxy for immobilizer presence. If no WCM messages are observed, it skips PIN entry. The record cites incorrect behavior order and handling issues. Timing and protocol details are withheld pending vendor remediation. CVSS is 2.4: AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
Likely exposure
Exposure appears limited to Indian Motorcycle Scout Bobber + Tech 2025 models with the Infotainment Digital Round display. The source does not identify other model years, other Indian Motorcycle products, or a specific firmware range.
Exploitation context
The CVE describes an adjacent-network attacker who can silence WCM traffic during boot, including through a separately tracked CAN bus-off technique. It does not report public exploit availability or active exploitation. KEV status is false in the provided bundle.
Researcher notes
The record withholds timing and protocol details. Avoid assuming broader CAN compromise from this CVE alone. The weakness is the boot-time decision order: absence of WCM traffic leads to skipping PIN. Evidence is limited to the CVE description and CWE reference.
Mitigation direction
- Check Indian Motorcycle or dealer guidance for firmware updates or service actions.
- Do not rely on the display PIN as the only protection for sensitive information.
- Limit unsupervised physical access to affected motorcycles until vendor guidance is available.
- Track the separately referenced CAN bus-off issue if disclosed by the vendor.
Validation and detection
- Inventory 2025 Scout Bobber + Tech motorcycles with Digital Round displays.
- Confirm current infotainment firmware and ask the vendor or dealer about affected builds.
- Review whether the display exposes personal data when unlocked.
- Monitor CVE and vendor channels for remediation details.
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-636: 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-696: 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-49318 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
- Low
- CVSS
- 2.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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:L/I:N/A:N0.91.4ASRGCVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N——ASRGVulnerability scoring details
Base CVSS 4.0 score
1LowVector: CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
2.4LowVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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/696.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.
Not Failing Securely ('Failing Open')
Not Failing Securely ('Failing Open') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Behavior Order
Incorrect Behavior Order 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.