Public vulnerability disclosure

CVE-2026-121147

Security Misconfiguration Vulnerability in Tata Motors iRA and iRA.ev mobile application

publishedCWE-295

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.

Technical severity8.5 highCVSS 4.0 · CNA: CERT-In
Published2026-11-04Source updated 2026-11-04
Collected2026-11-041 attributed source

Fixes and workarounds

Fix

Upgrade to latest versions: Tata Motors iRA 2.0 to version 26.8.2 Tata Motors iRA.ev to version 26.9.1

Source: CNA: CERT-In

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
Tata Motors iRA 2.0
Tata Motors
versions 26.7.3 and below (affected)
Other versions: unaffected
CNA: CERT-In
Tata Motors iRA.ev
Tata Motors
versions 26.7.2 and below (affected)
Other versions: unaffected
CNA: CERT-In

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
4.0 / 8.5
high
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NCNA: CERT-In

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide