2023 Mercedes-Benz EQE 350 4MATIC

Severe, life-threatening autonomous safety system and powertrain failures in a 2023 Mercedes-Benz EQE SUV. The vehicle exhibits sudden, violent unintended acceleration, unprovoked emergency braking, and steering lockups. On multiple occasions, including at 75 MPH on the freeway and 45 MPH on city streets, the vehicle abruptly applies maximum braking force down to a near-stop without driver input or any road obstruction, nearly causing multiple catastrophic rear-end collisions with semi-trucks and buses. Conversely, the vehicle experiences sudden unintended acceleration; during one severe city street incident, the vehicle unexpectedly accelerated from 40 MPH to 60 MPH while the driver was actively braking, causing the brake pedal to feel completely locked, stiff, and unresponsive for several seconds before stopping. While stopped at red lights, the vehicle violently surges and rocks forward/backward as if wanting to accelerate without driver input. The steering assistance system abruptly locks up or pulls hard to the right without warning, requiring the driver to physically wrestle control to maintain lane alignment. The braking system suffers from severe malfunctions, including the pedal randomly repositioning itself lower while driving and dropping completely to the floor during parking, causing the vehicle to roll until pumped. The electronic parking brake intermittently fails to release when shifting into drive/reverse. Additional systemic electrical and safety defects include: complete instrument cluster/gauge blackouts impairing speed monitoring; steering wheel physically blocking gauge visibility; total failure of rearview/surround-view cameras, blind spot monitors, and mirror controls; exterior door handles failing to deploy; rear trunk malfunctions; severe high-voltage battery range loss; and continuous infotainment/navigation crashes. Authorized dealerships have failed to repair these critical safety components across 4 distinct repair attempts.

NHTSA ID

11742218

Incident

Sep 1, 2024

Severe, life-threatening autonomous safety system and powertrain failures in a 2023 Mercedes-Benz EQE SUV. The vehicle exhibits sudden, violent unintended acceleration, unprovoked emergency braking, and steering lockups. On multiple occasions, including at 75 MPH on the freeway and 45 MPH on city streets, the vehicle abruptly applies maximum braking force down to a near-stop without driver input or any road obstruction, nearly causing multiple catastrophic rear-end collisions with semi-trucks and buses. Conversely, the vehicle experiences sudden unintended acceleration; during one severe city street incident, the vehicle unexpectedly accelerated from 40 MPH to 60 MPH while the driver was actively braking, causing the brake pedal to feel completely locked, stiff, and unresponsive for several seconds before stopping. While stopped at red lights, the vehicle violently surges and rocks forward/backward as if wanting to accelerate without driver input. The steering assistance system abruptly locks up or pulls hard to the right without warning, requiring the driver to physically wrestle control to maintain lane alignment. The braking system suffers from severe malfunctions, including the pedal randomly repositioning itself lower while driving and dropping completely to the floor during parking, causing the vehicle to roll until pumped. The electronic parking brake intermittently fails to release when shifting into drive/reverse. Additional systemic electrical and safety defects include: complete instrument cluster/gauge blackouts impairing speed monitoring; steering wheel physically blocking gauge visibility; total failure of rearview/surround-view cameras, blind spot monitors, and mirror controls; exterior door handles failing to deploy; rear trunk malfunctions; severe high-voltage battery range loss; and continuous infotainment/navigation crashes. Authorized dealerships have failed to repair these critical safety components across 4 distinct repair attempts.

NHTSA ID

11742216

Incident

Sep 1, 2024

1. March 11th: First Incident was when crossing a railroad crossing in [XXX] ~2:00pm the car suddenly braked and seatbelts tightened very strongly and immediately stopped, Automatic braking was engaged. There was a car Behind me and barely was able to brake and avoid rear ending me. We took it to dealer in Fremont (mb of fremont) a service advisor checked the car and drove it for a while (Joe Defraeitas) they were not able to find any issue and sent us back. asking us to bring it back if it happens again. my speed was between 30-40mph. I don't remember if there was lights flashing warning or not. all I remember it suddenly halted and stopped and I was really scrared. 2. March 17th at a very close time to ~2:00PM at exactly same place this issue happened again, this time I was with my daughter [XXX] ) and same exact thing happened; luckily no cars were behind me at that time again, same as before speed 30-40mph and no warning lights that I remember. this time we took the car to service dealership on March 20th and they asked us to schedule an appoint and we did bring it back on march 26th. The RO# from mboffremont is XXX; again same advisor. they claimed they checked all the software and sensors and nothing wrong with the car. 3. Third incident on Apr 7th at ~12:00 on [XXX] [XXX] by the railroads crossing as well, luckily no cars were behind me and speed was 20-30mph this time is didn't do full stop. We reported it this time to MB dealership in Pleasanton, CA. This was the original dealership where we bought the car. again they claim nothing is wrong with the car. The service manager mentioned that will look inot this carefully, but unfortunately a service advisor called and said nothing is wrong with the car and they were not able to (Service Advisor is [XXX] ). INFORMATION REDACTED PURSUANT TO THE FREEDOM OF INFORMATION ACT (FOIA), 5 U.S.C. 552(B)(6)

NHTSA ID

11730020

Incident

Mar 11, 2026

While driving down the highway late at night, with no other cars around, the panoramic sunroof exploded, throwing shattered glass everywhere. The window was not hit by an object and had no previous damage. Shattered flying glass while moving at highway speeds caused a momentary loss of control.

NHTSA ID

11729549

Incident

Apr 4, 2026

ALL TIRES MENTIONED HERE ARE PIRELLI ZERO RUN FLAT TIRES (MBQ-8-40-3071, PIRELLI 255/35R21) My Mercedes EQE equipped with 21” AMG wheels has suffered six blowouts using Pirelli ride fat tires that came with the car. It seems the car is too heavy for this tire/wheel configuration, which is a standard option and was installed on the car when I leased it. EQE, EQS, and S Class owners have reported the same problem in online forums over the last several years, specifically with 21” AMG wheels and ride Yat tires. All cases of this happening presented immediate risks, fortunately no crash occurred. Four incidents damaged one front tire, one incident damaged a front and rear tire. Mercedes should recall vehicles with this wheel and tire combination. The car has just 22,000 miles, bringing the mean time between failure for six tires to just 3,667 miles — well below the norm. I have owned many cars and typically average about 75,000 or more miles per tire, and never have catastrophic blowouts. The blowouts seem to occur because the Pirelli ride-flat tires have exceptionally stiff sidewalls that appear to fail under lateral impact resulting from even the most minor road imperfections. The car’s forward camber, low center of gravity, and heaviness exacerbate the problem. Two blowouts occurred while transiting over standard slightly recessed steel manhole covers traversed by thousands of vehicles daily. I have driven other Mercedes loaner vehicles with no incident. The problem appeared within a week of vehicle lease (May 2023) and I lost three tires in October 2025, within days of each other: once the day after a prior repair. I was also stuck waiting for repairs on a busy highway for 3 hours. This is a dangerous situation and needs a recall. Once is bad luck, twice is peculiar, three times is a pattern, four times is a design Yaw, and six times it’s negligence. I think the car is great otherwise but this is a dangerous design flaw and needs to be addressed by the company.

NHTSA ID

11696352

Incident

Oct 18, 2025

My Mercedes EQE equipped with 21” AMG wheels has suffered six blowouts using Pirelli ride flat tires that came with the car. It seems the car is too heavy for this tire/wheel configuration, which is a standard option and was installed on the car when I leased it. Various EQE, EQS, and S Class owners have reported the same problem in online forums over the last several years, specifically with 21” AMG wheels and ride flat tires. All cases of this happening presented immediate risks, fortunately no crash occurred. Four incidents damaged one front tire, one incident damaged a front and rear tire. Mercedes should recall vehicles with this wheel and tire combination. The car has just 22,000 miles, bringing the mean time between failure for six tires to just 3,667 miles — well below the norm. I have owned many cars and typically average about 75,000 or more miles per tire, and never have catastrophic blowouts. The blowouts seem to occur because the Pirelli ride-flat tires have exceptionally stiff sidewalls that appear to fail under lateral impact resulting from even the most minor road imperfections. The car’s forward camber, low center of gravity, and heaviness exacerbate the problem. Two blowouts occurred while transiting over standard slightly recessed steel manhole covers traversed by thousands of vehicles daily. I have driven other Mercedes loaner vehicles with no incident. The problem appeared within a week of vehicle lease (May 2023) and I lost three tires in October 2025, within days of each other: once the day after a prior repair. This is a dangerous situation and needs a recall. Once is bad luck, twice is peculiar, three times is a pattern, four times is a design flaw, and six times it’s negligence. I think the car is great otherwise but this is a dangerous design flaw and needs to be addressed by the company.

NHTSA ID

11696247

Incident

Oct 18, 2025

It happen 4 times during normal driving on local roads on nice weather and no car infront . My car just stop violently and make a lound noise as if it hit something .It happen very quick and became normal as if nothing wrong .Reported and brought car to dealer after a week there not found any defects.The 5th times happen when car pull out from driveway with no car around. I belived this a saferty hazard because if it happen during driving on hiway i could get hit from behide for sudden stop.

NHTSA ID

11664231

Incident

Jun 1, 2025

Complaint During part of the steering movement, it feels heavier or more difficult to steer in the same spot every time. OR Rattling, humming, dry sliding/gravel noise from the electric steering system when steering (see attachment). Complaint does not impact the ability to safely steer or control the vehicle. Cause Ball screw drive (KGT) of electric steering damaged by: 1. External force due to: ‑ Hitting the curb/posts with the front wheels. ‑ Driving over obstacles (e.g. pothole/ threshold/ speed bump/ gully) at an inappropriate speed. 2. Corrosion/ water ingress through a damaged boot (see attachment). ‑ Cracks (1) ‑ High pressure cleaner (2) ‑ Animal bite (3) See various examples listed in the attachments for examples of outside influence. Remedy Remove boot clamps closest to steering gear housing on both left and right (as seen in "Steering Rack Boot Clamp Location"). Pull back boot and inspect for rust, broken end stops, water, or any other anomalies. Replace electric steering. Note: Steering gears replaced due to outside influence or damage must not be claimed under warranty!

Complaint Tailgate opens unintentionally. Cause Accidental or unnoticed activation of the button to open the tailgate on the vehicle key. EXAMPLE: when stored in trouser pocket, handbag etc. Remedy As of the 6th generation, the vehicle key can be recoded so that the tailgate no longer opens as a result of a long press on the button, but by double‑clicking on the button instead. This reduces the likelihood of the button being activated accidentally or unintentionally. The recoding can be carried out as follows: 1. Add SA Code O19 into VeDoc (O for Oscar, not "zero") • an XSS ticket may be necessary to add the SA code 2. Perform SCN coding of EIS N73 control unit 3. Deactivate the vehicle key (a successful deactivation is indicated by the LED lighting up 2x briefly and then 1x for a long period). 4. Place the vehicle key in the storage compartment on the key symbol and turn on the ignition. IMPORTANT: all other vehicle keys must be outside the recognition range of the vehicle when doing this! Perform steps 3 and 4 successively for all vehicle keys. Notes: 6th, 7th and 8th generation keys can be deactivated as follows: Up to modification year 22/1 by double clicking the "Lock button" As of modification year 22/1, by press and holding the “Lock button", then double‑click the “Unlock button" at the same time. On model series 167, the storage compartment with the key symbol is located in the armrest. The SCN coding from the EZS is only transferred correctly to the vehicle key under the following conditions: Only one vehicle key is located in the vehicle, this key has been deactivated and it is positioned on the marking in the storage compartment for the data transfer. The costs for this adaptation are to be borne by the customer. For the newer BR 174, 178, 244, 248, 520, and 540, a software update must be initiated, as there is no way to perform SCN coding.

Complaint Traffic sign symbol for "Traffic Sign Assist" is blinking in instrument cluster without obvious cause usually with one of the following scenarios: • Flashing without a speed limit ("‑ ‑"). • Flashing when current vehicle speed is under speed limit. • Flashing between US speed limit symbol and European speed limit symbol. NOTE: • Verify that the concern falls under one of the attachment videos. If not, then it is outside of the scope of this LI. • This also does not cover "Traffic Sign Inoperative" messages on the instrument cluster. Cause There are two identified reasons for this concern: 1. Country code information stored incorrectly at a particular geographic latitude range. 2. Incorrect reference data when the vehicle is started and a GPS signal is not immediately available. Remedy Update head unit software to latest version and the re‑check function in the same location. If vehicle is still exhibiting one of the symptoms as described exactly as in the complaint section or as shown in the video attachments, open a TIPS case to the Body/Chassis/Entertainment inbox with the following: • Video of the concern. • Exact location (latitude and longitude is best)

Complaint The following most common complaints may be observed: • Brief connectivity interruptions when using Apple CarPlay over Wi-Fi • Audio cuts out • Device not recognized • No operation possible Cause There are multiple possible causes for an iPhone disconnecting from a vehicle’s head unit while using Apple CarPlay. These include hardware, software, and environmental factors: Environmental Interference External Sources: • Passing under toll bridges, driving near airports, or areas with heavy electronic interference (e.g., as described in LI82.85-P-076157) can cause connection drops. Cellular Networks: • Interference from nearby cell towers operating on similar frequencies (usually 2.4GHz or 5GHz) can disrupt the signal. Storage Location: • Keeping your phone in a handbag or surrounded by other objects inside the vehicle can create physical or electronic interference. Device and Software Issues Head Unit Software/Hardware: • Outdated firmware, bugs, or hardware faults in the vehicle’s head unit can prevent a stable connection. iPhone Software/Hardware: • Similar issues in the iPhone, including buggy iOS updates or hardware problems, may affect performance. Reset or Reboot:• Automatic rebooting or resetting of either the head unit or the iPhone will temporarily disrupt CarPlay. Connection and Settings Wired Connections: • Faulty Cable: A damaged or poor-quality USB cable can cause intermittent or total loss of connection. • USB Port Issues: Dust, debris, or physical damage in the USB port of either the head unit or the iPhone can also lead to disconnects. Wireless Connections: • Intermittent Bluetooth/Wi-Fi: Unstable wireless communication (Bluetooth/Wi-Fi) can frequently break the Car- Play connection. Power Management: • Battery Saver Mode: Enabling low power mode may restrict background processes, affecting CarPlay. • Vehicle’s Electrical System: Unstable power delivery from the car’s battery or electrical interruptions can cause the head unit to malfunction. Phone & App Configuration Phone Settings: • Incorrect or conflicting settings (especially Bluetooth or Wi-Fi) on your iPhone can interfere with the CarPlay link. • Third-Party Apps/Profiles: • Installed apps or configuration profiles may conflict with CarPlay’s operation. • Native apps are apple maps, apple music, audio books, apple news, podcasts, messages and phone. All other apps are considered third party apps. App Conflicts: • Running conflicting apps that require similar system resources as CarPlay can cause instability. Mobile Data Plan: • Streaming from online sources without sufficient mobile data can result in lost connectivity. Other Factors Heat & Overheating: • If either the phone or the head unit overheats, they may disable certain functions to prevent damage, leading to disconnection. User Actions: • Accidentally disconnecting the device in settings, or physically moving or bumping the phone or cable, may disrupt the connection. Remedy FUP6 (E605.8) software has been released for the following chassis: 118, 177, 243,247,206,254,167,294,295,296,223, 297. Flash available software for the head unit and test for function. The LI will be updated once available for the remaining chassis. If the complaint remains after the SW update please continue with the steps below. Guided Diagnostic Path for Apple CarPlay Connection Issues: Please follow the steps below to systematically diagnose and resolve CarPlay concerns:Update Devices: • Ensure the iPhone is updated to the latest available iOS version. • Ensure the vehicle’s head unit is updated to the latest software version available. Isolate the Issue: • Check whether the symptom persists with another iPhone running the latest iOS version. • Test both wireless and wired CarPlay connections: • Does the issue only occur with wireless CarPlay? • Does the wired connection to the phone function correctly? Further Troubleshooting Steps: • Reboot the iPhone. See attachment for further instructions.

Complaint 1. General Diagnostic Tips 2. One or More PARK Sensor Activations 3. Red Ring Around Vehicle 4. "Active Parking and Parking Assist Inoperative" on Instrument Cluster 5. Cameras 6. Other Park Topics. Cause Various root causes Remedy See attached diagnostic guide.

Complaint Customer Complaint: - AC charging is not possible. - The departure time, charging pause, location-based charging or target SOC limit is automatically set to 50% or to a random value in the Mercedes me application or in the charging settings on the head unit display. (Picture 1 & 3) - Incorrect notifications appear in the Mercedes me application for charging-related functions. (Picture 2) Related DTCs in quick test: No related fault codes (DTCs) are stored in the relevant control units. CPC3 - N127 (Drivetrain control unit) OBL223_GEN4 - N83/11 (Alternating current charger for high-voltage battery) DCB223 - N116/5 - Direct current charge connection unit (DCCU) Picture1 The target SOC limit is automatically set to 50% or any random values during charging. Picture 2 Incorrect notification Example “Unable to unlock charging cable. Picture 3 Incorrect settings of charge interruption or pause. (If applicable) Cause - The Customer shares their Mercedes me credentials (password) with a third-party application, for example, a wall box application. This causes the Mercedes Benz backend server to receive random requests to reset the maximum SOC, departure time, charging pause, etc. - Charging settings are set incorrectly, for example, incorrect departure time, charging program, charging interruption/ pause, etc. Remedy The remedies below may vary depending on the customer complaint. Refer to the remedy that best matches the customer complaint. Remedy 1: The target SOC limit is automatically set to 50% or to random values during charging. - Change the Mercedes me login password on the Mercedes me homepage. (My Account > Login and Security > Reset). (Refer to Annex 1). Previously granted authorizations should then be revoked so that the charging settings can no longer be changed by external applications. Advise customers not to share the new password again. - Are there any sub-users? If yes, revoke their rights and reassess the function. -If differences between the vehicle and the Mercedes me app are visible, a new synchronization is recommended. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. Remedy 2: Incorrect notifications in the Mercedes me app for charging-related functions. - Restart synchronization between the app and backend. Turn off Digital Extras through the Mercedes me app or the MMCR portal, and then turn the services on again. (Refer to Annex 2) Remedy 3: Incorrect charge interruption or pause setting. - Perform a factory reset of the head unit (A26/17). (Home > Functions > System > Reset), or turn off/correct all charging settings. (Refer to Annex 3) Additional Information: (Good to know) The LED on the charging inlet or socket indicates whether charging is completed or paused. 1) If the target SOC is reached, the charging inlet LED lights up Blue/Green without flashing. 2) If charging is paused, the charging inlet LED lights up orange without flashing. Additionally, the head unit charging settings display a charging pause. Note: Do not replace any hardware components for these complaints. If the complaint cannot be solved, please contact via TIPS or CAC.