📧 info@texaslemonlaw.com 📞 +1 866 777 5045
Free Consultation Available

2025 RIVIAN R1T

View all complaints and recalls for this specific model year.

2025 RIVIAN R1T Summary

2025

Model Year

2

Total Complaints

4

Total Recalls

52655

Vehicles Affected

Recalls

2025 RIVIAN R1T

536 vehicles affected

25V370000

SEAT BELTS:FRONT:ANCHORAGE

Rivian Automotive, LLC (Rivian) is recalling certain 2022-2025 R1T and R1S vehicles. The D-ring bolts for one or both front seat belt anchorage assemblies may not have been properly installed.

Risk: An improperly secured seat belt may not restrain an occupant as intended, increasing the risk of injury during a crash.

2025 RIVIAN R1T

24214 vehicles affected

25V585000

ELECTRICAL SYSTEM:ADAS:AUTONOMOUS/SELF DRIVING:SOFTWARE

Rivian Automotive, LLC (Rivian) is recalling certain 2025 R1S and R1T vehicles operating a software version prior to 2025.18.30. The Hands-Free Highway Assist (HWA) software may fail to correctly identify a lead vehicle.

Risk: Failure to detect another vehicle increases the risk of a crash.

2025 RIVIAN R1T

27882 vehicles affected

25V387000

EXTERIOR LIGHTING:TURN SIGNAL

Rivian Automotive, LLC (Rivian) is recalling certain 2025 R1S and R1t vehicles. One or both front turn signals may fail to illuminate and flash. As such, these vehicles fail to comply with the requirements of Federal Motor Vehicle Safety Standard (FMVSS) number 108, "Lamps, Reflective Devices, and Associated Equipment."

Risk: Turn signals that do not function properly, failing to indicate the driver's intention to change direction, increase the risk of a crash.

2025 RIVIAN R1T

23 vehicles affected

25V537000

ELECTRICAL SYSTEM:PROPULSION SYSTEM:TRACTION BATTERY

Rivian Automotive, LLC (Rivian) is recalling certain 2025 R1S and R1T vehicles. An improperly grounded connection inside the High Voltage Distribution Box (HVDB) may cause a loss of drive power.

Risk: A loss of drive power increases the risk of a crash.

Complaints

2025 RIVIAN R1T

ID: 2129013

SUSPENSION

I leased my Rivian on June 28th. Around July 21st, the vehicle started to drift to the left. On August 19th, my vehicle started to develop bump steer over uneven road surfaces. I brought my vehicle in for service on August 20th. From August 20th to now, my vehicle has had 3 alignments performed, none of them have been maintained spec. Attached are screenshots/pictures of the alignments. Between the first and second alignment the vehicle was driven about ~50 miles. Between the second and third it was driven about another 50 miles. I do not have exact mileage as Rivian has not released service records to me. My vehicle does not track straight on any surface. In addition, because of the regenerative breaking of the Rivian, when you stop the vehicle it pulls significantly to the right, approximately a half lane for every 75 feet. My concern is that the vehicle cannot maintain an alignment over the course of ~110 miles, does not track straight, exhibits bump steer, and Rivian has no available solve to this behavior.

2025 RIVIAN R1T

ID: 2129012

STEERING

I leased my Rivian on June 28th. Around July 21st, the vehicle started to drift to the left. On August 19th, my vehicle started to develop bump steer over uneven road surfaces. I brought my vehicle in for service on August 20th. From August 20th to now, my vehicle has had 3 alignments performed, none of them have been maintained spec. Attached are screenshots/pictures of the alignments. Between the first and second alignment the vehicle was driven about ~50 miles. Between the second and third it was driven about another 50 miles. I do not have exact mileage as Rivian has not released service records to me. My vehicle does not track straight on any surface. In addition, because of the regenerative breaking of the Rivian, when you stop the vehicle it pulls significantly to the right, approximately a half lane for every 75 feet. My concern is that the vehicle cannot maintain an alignment over the course of ~110 miles, does not track straight, exhibits bump steer, and Rivian has no available solve to this behavior.