> CVE TRACKER — INDIA FOCUS_
Critical vulnerabilities affecting software and systems widely deployed in Indian enterprise, government, and banking environments. Sources: NVD, CERT-In advisories, CISA KEV catalog. Prioritized for India-relevant technology stack.
| CVE ID | CVSS | Product / Affected System | Description & India Impact | Patch | KEV |
|---|
Vulnerability Intelligence for Indian Organisations
A CVE (Common Vulnerabilities and Exposures) identifier is a unique reference for a publicly known security flaw. Tracking CVEs is how security teams move from a flood of disclosures to a short list of issues that actually matter for their environment. The challenge is rarely a shortage of vulnerabilities — it is deciding which few, out of thousands, to fix first.
From severity score to real-world priority
The CVSS score describes a vulnerability’s theoretical severity, but severity alone is a poor guide to risk. Two signals sharpen the picture: whether a flaw appears on the United States CISA Known Exploited Vulnerabilities (KEV) catalogue, which lists issues being actively exploited in the wild, and the EPSS probability that a flaw will be exploited soon. A vulnerability that is exposed to the internet, present on a critical asset, and listed in KEV deserves attention long before a higher-scored flaw that no one is attacking.
Compliance and reporting in India
Indian organisations operate under specific obligations. CERT-In issues regular advisories that should feed directly into patch planning, and its directions require that certain cyber incidents be reported within a defined window of being noticed. Treating vulnerability management as a documented, prioritised process — rather than an ad-hoc scramble after each disclosure — is both better security and easier to defend during an audit or investigation.
How to use this tracker
- Match each entry against your asset inventory: product, version and whether it is internet-facing.
- Prioritise vulnerabilities listed as known-exploited, then those with public exploit code, then the rest by CVSS score.
- Apply the vendor fix or documented mitigation; record the date and the evidence of closure.
- Hunt for signs of earlier exploitation in logs for the period before patching — patching does not remove an attacker who is already inside.
- If exploitation is confirmed, report to CERT-In within six hours under the April 2022 directions.
Reading CVSS scores sensibly
A CVSS base score describes how severe a flaw is in general, not how risky it is for you. An internet-facing system with a 7.5 that is being actively exploited is a higher priority than an internal system with a 9.8 that nobody can reach. Combine the score with exposure, exploitation evidence and the value of the data on the system. For regulated entities, document the reasoning: auditors look for a consistent, risk-based patching policy rather than a list of patched CVEs.
Frequently asked questions
Where does the vulnerability data come from?
From public sources including the US National Vulnerability Database, CERT-In advisories and CISA's Known Exploited Vulnerabilities catalogue, selected for software widely deployed in India.
Does a listed CVE mean my systems are vulnerable?
Only if you run the affected product and version and it is reachable by an attacker. Match each entry against your asset inventory before acting.
What should I do if a CVE was exploited on my network?
Contain the affected systems, preserve logs, apply the fix, and report to CERT-In within six hours if the incident is a reportable one under the April 2022 directions.
How is a CVE different from a CERT-In advisory?
A CVE is a global identifier for a single vulnerability. A CERT-In advisory is guidance for Indian organisations and may cover several CVEs, affected products and recommended actions.