CVE-2026-121147Tata Motors iRA 2.0 improper certificate validation
CVE-2026-121147 is a improper certificate validation in Tata Motors iRA 2.0, rated high (8.5 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Deferred
What it is
TLS certificates are not checked properly, so an attacker on the path can pose as the server.
How it is reached
An attacker can exploit it from the same local network segment, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects and change data or behaviour. In practice, this kind of flaw lets an attacker read or tamper with traffic, or pass a forged message as genuine.
Is it being exploited?
There is no public report of exploitation yet. EPSS estimates a 0.09% chance of exploitation activity in the next 30 days, higher than 0% of scored CVEs.
What to do
- No fixed version is listed yet. Find every place Tata Motors iRA 2.0 runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- Segment the networks that can reach it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to improper implementation of SSL certificate pinning in the network security configuration, resulting in ineffective certificate pinning controls. An attacker positioned to intercept network traffic could exploit this vulnerability to intercept or modify communications between the application and its backend services.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- TLS termination and service-to-service channels. The flaw sits on the network path between clients and services.
- Signature checks. The flaw sits on the network path between clients and services.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- People who open files and links. Mail, chat and browsers are the delivery path.
- On the network path between clients and services. An attacker who crosses it can read or tamper with traffic, or pass a forged message as genuine.
Questions to answer about your own systems
- Where does Tata Motors iRA 2.0 run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.