# CVE-2026-121147: Security Misconfiguration Vulnerability in Tata Motors iRA and iRA.ev mobile application


- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 4 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-8x7g-wrmc-g29j

## What is CVE-2026-121147?

CVE-2026-121147 is a high-severity vulnerability in Tata Motors iRA 2.0, published on 4 Nov 2026. 

### Official description

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.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-121147?


## How do I fix CVE-2026-121147?

No fix has been published for CVE-2026-121147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121147 being exploited?

There is no known exploitation of CVE-2026-121147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121147 and fix it if it is affected.

What it is: CVE-2026-121147 is a high-severity vulnerability in Tata Motors iRA 2.0, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121147 in the wild and no public exploit code.

Affected product: Tata Motors iRA 2.0. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121147/ (Markdown: https://insights.sbomify.com/CVE-2026-121147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121147
- OSV: https://osv.dev/vulnerability/CVE-2026-121147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121147/
Summaries are generated and may contain mistakes; the official description above is the record.
