Tata Motors vulnerabilities
Every vulnerability this feed holds for Tata Motors, merged from five public registers and ordered by what warrants attention first — exploited in the wild, then CVSS, then recency.
4 vulnerabilities tracked.
- 8.8 This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to presence of hardcoded service account credentials, API Keys…
- 8.5 This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to improper implementation of SSL certificate pinning in the…
- 7.1 This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to insufficient validation of URLs and origins loaded within…
- 6.8 This vulnerability exists in the iRA 2.0 and iRA.ev mobile applications due to the recording of authentication tokens in application logs…
What this covers
This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Tata Motors is free of vulnerabilities.
Query this from an agent over MCP · Check a lockfile by version
Other vendors tracked here
Google Microsoft Red Hat Apple zephyrproject Apache Software Foundation n/a Hewlett Packard Enterprise (HPE) MediaTek, Inc. Linux Unknown Eclipse Foundation FreeRDP Dell Oracle Corporation MONGODB Gitea WAVLINK vercel Tanium vim jpadilla IBM WSO2