India’s Computer Emergency Response Team (CERT-In) has rated its advisory concerning four vulnerabilities in Tata Motors’ iRA 2.0 and iRA.ev connected-car applications as high severity and advised users to install fixed versions. The government vulnerability note was originally issued on 4 November 2026 and the CERT-In page was last updated on 17 November 2026. It applies to iRA 2.0 version 26.7.3 and earlier, and iRA.ev version 26.7.2 and earlier.
The required versions are specific: CERT-In tells iRA 2.0 users to update to version 26.8.2 and iRA.ev users to update to version 26.9.1. Owners should check the version shown in the app’s settings or store listing rather than assuming that automatic updates have already completed.
Tata iRA security update: which versions are affected?
CERT-In describes iRA 2.0 as the connected-vehicle application for Tata’s internal-combustion-engine customers and iRA.ev as the corresponding application for electric-vehicle customers. These apps can present vehicle status, health and trip information and can support remote commands. That scope is why weaknesses involving credentials or session tokens require prompt attention.
- iRA 2.0: versions 26.7.3 and below are listed as affected; update to 26.8.2.
- iRA.ev: versions 26.7.2 and below are listed as affected; update to 26.9.1.
The advisory does not say that every user has been compromised. It explains what an attacker could potentially do if the weaknesses were successfully exploited. We should therefore distinguish a vulnerability from evidence of an actual incident affecting a particular owner.
What the four CERT-In vulnerabilities mean
The first issue, CVE-2026-121144, concerns hardcoded service-account credentials, API keys and authorisation tokens within an application package. CERT-In says an unauthenticated remote attacker could download the package and extract embedded information, potentially gaining access to associated backend services.
CVE-2026-121145 concerns insufficient validation of URLs and origins loaded through a WebView component. A malicious web payload sent to an affected WebView could, according to the note, interact with app functions, obtain a live bearer token and potentially impersonate the user.
The third issue, CVE-2026-121146, involves authentication tokens being recorded in development or debugging logs. This attack path is different because CERT-In describes a local attacker with access to the logs retrieving and misusing exposed session tokens.
CVE-2026-121147 concerns ineffective SSL certificate pinning. CERT-In says an attacker positioned to intercept network traffic could potentially intercept or alter communication between the app and its backend services. These are distinct technical paths, even though several lead to the common risk of unauthorised access or user impersonation.
What Tata iRA and iRA.ev users should do now
First, open the relevant Apple App Store or Google Play listing and check whether an update is pending. After installing it, verify the installed version inside the app or the phone’s application-information screen. The target numbers are 26.8.2 for iRA 2.0 and 26.9.1 for iRA.ev.
Second, avoid installing the app from an unofficial APK repository or following an update link delivered through an unsolicited message. Use the official app store on the phone. If the app was installed from another source, remove it and obtain the official Tata Motors application after confirming account-recovery details.
Third, review recent account activity and vehicle notifications for commands or changes that are not recognised. CERT-In’s note does not provide a consumer incident-response procedure, so owners who see unexplained activity should contact Tata Motors through an official support channel. Changing reused passwords on other services is also sensible if the same credentials were used elsewhere.
Finally, treat the mobile phone as part of the connected-car security boundary. Keep the operating system current, use a device lock, and avoid granting unnecessary accessibility or screen-sharing permissions. Our engine immobiliser explainer covers a different security layer—the coded key and vehicle start authorisation—while the iRA advisory concerns a connected-services application. For comparison, our earlier Toyota i-Connect feature coverage shows how remote commands and app permissions also form part of another manufacturer’s connected-car ecosystem.
What the advisory does not establish
The note does not identify a confirmed number of affected customers, claim that vehicles were taken over, or state that the vulnerabilities caused crashes. It also does not replace model-specific service advice. The concrete action available to owners is to update the correct application to the fixed version and monitor the associated account.
Because iRA 2.0 and iRA.ev serve different vehicle groups, users should not substitute one version number for the other. The safest completion check is simple: confirm the app name, confirm the installed version and retain the normal official support path if an account or remote command behaves unexpectedly.
Graphic credit: BeyondHorsepower Editorial Team.
0 comments