Ford recalls 272K EVs over rollaway risk | Analysis by Brian Moineau

A familiar wobble in the EV transition: Ford recalls more than 270,000 vehicles over roll-away risk

You’re halfway through your day, you click the car into Park, and—nothing obvious seems wrong. But a nagging software glitch could mean “Park” didn’t actually secure the drivetrain. That’s the blunt problem behind Ford’s latest recall: a software issue in the integrated park module that can let certain electric and hybrid vehicles roll away.

This recall landed December 19, 2025, and it’s one more reminder that the shift to electrified powertrains is as much about software reliability as it is about batteries and motors. (abcnews.go.com)

Highlights you can skim

  • Ford is recalling roughly 272,645 vehicles in the U.S. over an integrated park module that may fail to engage Park. (reuters.com)
  • Affected models include select 2022–2026 F-150 Lightning BEVs, 2024–2026 Mustang Mach‑E crossovers, and 2025–2026 Maverick pickups. (fordauthority.com)
  • Ford will provide a free software update delivered over-the-air (OTA) or at dealers; owner notices are expected beginning February 2, 2026. (fordauthority.com)

Why this matters beyond a sticker headline

Automakers have long had mechanical fail-safes (parking pawls, physical linkages and mechanical brakes). With electrified drivetrains and more functions controlled by software, the safety envelope depends increasingly on code. That introduces a few realities:

  • Software can be patched remotely, which is faster than a traditional parts campaign — but OTA updates rely on a secure, reliable update process and that owners allow or receive them. (fordauthority.com)
  • Recalls affecting high-profile EV and hybrid models intensify scrutiny of testing and validation practices across the industry. Consumers expect EVs to be modern in both hardware and software; lapses undercut trust. (reuters.com)
  • Even when nobody has reported accidents or injuries, a potential rollaway is serious: vehicles that move unexpectedly can injure pedestrians, damage property, or start chain-reaction crashes. Regulators classify that as a meaningful safety risk. (reuters.com)

What Ford owners should know and do

  • Affected count and models: about 272,645 U.S. vehicles — certain F-150 Lightning (2022–2026), Mustang Mach‑E (2024–2026), and Maverick (2025–2026). (reuters.com)
  • Remedy: Ford will issue a free park-module software update, via OTA or at dealers. Owner notifications are scheduled to begin February 2, 2026. The recall is logged under Ford reference 25C69. (fordauthority.com)
  • Immediate practical steps: until you get the update, use the physical parking brake every time you park, avoid steep inclines when possible, and follow any owner-letter instructions. If you’re unsure whether your VIN is affected, contact Ford customer service at 1-866-436-7332 or check NHTSA. (abcnews.go.com)

Bigger picture: what this says about EVs and risk

This recall is not an indictment of electrification. It’s a snapshot of where we are: cars are now rolling computers on wheels, and that brings powerful benefits (remote fixes, analytics, smoother integration) but also new single points of failure. Regulators like NHTSA are adapting to software-driven recalls, and manufacturers are racing to balance speed-to-market with deeper software validation.

Two structural tensions show up here:

  • Speed vs. robustness: OTA updates let manufacturers fix issues faster than the old parts-and-dealer model, but pushing software updates at scale requires rigorous testing and a secure distribution pipeline. (fordauthority.com)
  • Perception vs. reality: frequent software-related recalls can fuel headlines that EVs are “unreliable,” even when fixes are straightforward and remedial. Communicating transparently and quickly is everything. (reuters.com)

My take

Recalls like this are frustrating but inevitable as vehicles become more software-defined. The good news: the fix is software, which Ford can distribute without waiting for physical parts. The not-so-good news: repeated software-related recalls risk eroding consumer confidence unless manufacturers pair fixes with clearer testing and faster, more proactive communication.

For owners, cautious behavior (using the parking brake until your update arrives) is prudent. For Ford and other automakers, the path forward is plain: invest more in pre-release software validation and make OTA rollouts bulletproof — because patches are only as good as the systems that deliver them.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.

Rivian Digital Key: Wallet-Based Access | Analysis by Brian Moineau

A key in your pocket: Rivian Digital Key brings Gen 2 cars into your phone wallet

There’s a tiny moment of delight when you walk up to your car, your phone in your hand (or not), and the vehicle simply knows you’re there. Rivian just made that moment more seamless. On December 18, 2025, Rivian began rolling out Rivian Digital Key for Gen 2 R1T and R1S vehicles — a native digital-wallet car key experience for iPhone, Apple Watch, Google Pixel, and Samsung devices that lets owners unlock, share, and start their Rivian without the dedicated fob or the Rivian app’s Bluetooth-only workflow.

This isn’t just another “app feature” patch. It marks a bigger shift toward platform-level convenience, tighter hardware integration (Ultra-Wideband and NFC), and the standardization of car access across ecosystems.

Why this matters now

  • Smartphones have increasingly replaced physical items (boarding passes, credit cards, transit passes). Car keys are the next obvious candidate — but only when the integration is reliable and secure.
  • Rivian’s Gen 2 cars were built with newer connectivity and UWB hardware that make native wallet keys practical in ways first-gen Bluetooth approaches weren’t.
  • By supporting Apple Wallet, Google Wallet, and Samsung Wallet, Rivian avoids locking users into a single OS and taps into the “works-as-you-expect” experience people now expect from modern devices.

What Rivian Digital Key does

  • Native wallet integration: Add your Rivian Gen 2 car key to Apple Wallet (iPhone & Apple Watch), Google Wallet (Pixel), and Samsung Wallet.
  • Multiple unlocking modes: Ultra-Wideband (UWB) for precise hands-free proximity; NFC fallback that can work even when the phone is in power-reserve (Rivian notes up to ~5 hours on supported devices).
  • Key sharing: Send digital keys to family and friends instantly — no physical handoffs.
  • Broader device support: Works across major smartphone ecosystems to maximize owner convenience.
  • Requirements and flow: The feature arrives with Rivian’s 2025.46 OTA and Rivian Mobile App update (3.8.0); some Android implementations require recent OS versions (Android 15 / One UI 7.0 mentions in reporting).

(Technical specifics and exact device compatibility can vary; check your vehicle’s OTA status and the latest Rivian app release notes before expecting the feature on your car.)

How this compares to the old way

  • Old: Rivian’s earlier digital key used the Rivian app and Bluetooth Low Energy. It worked, but could be slower, less precise, and was app-dependent.
  • New: Keys live at the OS level (Wallet apps), enabling Express/Power Reserve, tighter proximity detection through UWB, native watch support, and a fallback NFC path if the battery is depleted. In short: faster, more reliable, and more integrated.

The broader context

  • Rivian is part of a broader industry trend: automakers are adopting the Car Connectivity Consortium (CCC) standards and integrating with phone wallet ecosystems. Apple Car Key and similar Android standards have been rolling out across several manufacturers in recent years.
  • This update arrives alongside other notable 2025.46 features (Universal Hands-Free driving modes and other Gen 2 improvements), signaling Rivian’s push to refine both autonomy and convenience features in tandem.
  • The move also reflects product lifecycle strategy: many automakers concentrate new platform-level integrations on newer vehicle generations, which can leave earlier owners waiting or requiring hardware retrofits.

Opportunities and caveats

  • Opportunities:

    • Simpler sharing: temporary or permanent digital keys can replace lending physical fobs.
    • Reduced lockout worry: Express/Power Reserve offers peace-of-mind if your phone dies.
    • Cross-platform parity: support for iOS and major Android ecosystems lowers friction for households with mixed devices.
  • Caveats:

    • Compatibility: older phones or Gen 1 vehicles may not gain the same functionality.
    • Security and privacy: while wallet-based keys typically have strong device-level protections, owners should follow best practices (device passcodes, biometric locks, OS updates).
    • Reliance on hardware: UWB and NFC behaviors depend on device and vehicle hardware; real-world performance can vary by device model and environmental conditions.

What this means for owners and would-be buyers

  • Gen 2 Rivian owners should look for the 2025.46 OTA and update the Rivian app (3.8.0+), then follow the wallet setup flow to add the car key.
  • If you’re evaluating Rivian vs. other EVs, consider how important native wallet integration is to your daily routine. For many buyers, the convenience of wallet-based keys will be a useful tie-breaker.
  • If you own a Gen 1 R1 and hoped for parity, note that many of these features rely on Gen 2 hardware and may not be fully transferable without retrofits.

A few practical tips for setup

  • Update the Rivian mobile app to the version that mentions wallet support (3.8.0 or later) and ensure your vehicle has received the 2025.46 OTA.
  • For iPhone owners: confirm iOS 17.4.1+ and Wallet readiness; for Apple Watch, make sure NFC works and watchOS is up to date.
  • For Android owners: check Google Wallet or Samsung Wallet compatibility and any OS version requirements (reporting has referenced Android 15 / One UI 7.0 for some features).
  • Keep your device OS updated and enable device-level protections (Face ID/Touch ID, PIN/passcode) for security.

My take

Rivian Digital Key is one of those “small” features that changes daily life more than you’d expect — especially once you get used to your phone being the primary interface for everything. By moving car access into native wallets and leveraging UWB/NFC, Rivian has reduced friction and added resilience (power reserve) against common real-world annoyances. It’s also a vote of confidence in cross-platform standards: owners shouldn’t need to swap ecosystems to get convenience parity.

That said, manufacturers must balance excitement with clarity: clear communication about device and vehicle compatibility will be crucial to avoid confusion, particularly between Gen 1 and Gen 2 owners. If Rivian keeps this momentum — and continues to make ownership feel like a continuous software upgrade — these moments of polish could become a meaningful competitive advantage.

Final thoughts

Digital keys are a practical example of how cars are becoming platforms rather than standalone devices. When automakers, OS vendors, and standards groups converge on simple, secure experiences like this, the payoff is everyday delight: fewer fumbling moments at the door, easier sharing with family, and one less physical item to misplace. Rivian’s rollout for Gen 2 is a smart step in that direction — now it’s about execution, clarity, and getting the experience right for every owner and device.

Sources




Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.


Related update: We recently published an article that expands on this topic: read the latest post.