CVE-2026-49317
Raw vector
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-49317 is a low-severity Failing Open (CWE-636) vulnerability in Mitre (inferred from references). Its CVSS base score is 1.0 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Service Stop (T1489); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CP-12 (Safe Mode) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-33296
Vulnerability Data
Incorrect behavior order in the Infotainment / Digital Round display of the Indian Motorcycle Scout Bobber + Tech 2025 model year allows an adjacent-network attacker to bypass the PIN entry screen. The Infotainment uses presence of Wireless Control Module (WCM)…
more
traffic during its boot window as a proxy for whether an immobilizer is fitted; if no WCM messages are observed, it skips the PIN entry screen and shows the normal user interface. An attacker who silences the WCM during the boot window — for example via a separately tracked CAN bus-off technique — can present a fully unlocked Infotainment despite the PIN never being entered. Specific timing and protocol details have been withheld pending vendor remediation.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 2 OS baselines
V3.2.1V7.4.1V8.3.3V10.3.4
Mitigating Controls (NIST 800-53 r5) AI
SC-24 directly requires the system to fail to a known state that preserves security properties, structurally stopping fallback to a less-secure mode.
SI-17 mandates explicit fail-safe procedures that activate on indicated failures, preventing the insecure fallback behavior.
CP-12 forces entry into a safe mode on detected conditions, limiting exposure but not covering every failure path.
Developer testing and evaluation at post-design stages can discover incorrect ordering of related behaviors before deployment.
Input validation directly requires checking for unexpected or malformed conditions before they propagate.
Vulnerability scanning may surface order-related weaknesses after code is built but does not address their root cause.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices explicitly include designing error and failure handling to remain in a secure state.
Runtime monitoring of software and environments can detect adverse events triggered by unhandled exceptional conditions.
Least-privilege policy and enforcement directly counters the permissive-access fallback example in the CWE.
Hardened baselines and configuration management reduce the chance that error paths default to insecure settings.
Generating logs of exceptions and errors enables detection of improper handling of unusual conditions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect ordering flaws but does not prevent them during development.
Logging can record unhandled exceptions but does not prevent the weakness itself.
Monitoring may detect symptoms of unhandled conditions but does not eliminate the root weakness.
Secure development life cycle mandates correct sequencing of security activities, directly preventing incorrect behavior order.
Application security requirements explicitly call for handling of exceptional conditions and error paths.
Secure system architecture and engineering principles require proper ordering of design and implementation steps.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-754
- V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-754
Oracle Linux 9 (1 rule)
- V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-754