Every so often the digital tools we rely on quietly reveal a crack, and this week India's national cybersecurity watchdog, CERT-In, pointed to cracks in two widely used products: Google Chrome and GitLab. Reported on October 30, 2025, the warning asks people and administrators to act now, because a flaw in a browser can be reached by something as ordinary as a web page someone happens to open. The advisory points toward the remedy as well, linking the vendors' own updates, a reminder that trust in the tools we use is kept not by perfection but by the steady, unglamorous work of mending what is
India's CERT-In Flags Critical Flaws in Google Chrome and GitLab, Urges Immediate Patching
A page built to trigger the flaw could be enough to start the attack.
Every so often the digital tools we rely on quietly reveal a crack, and this week India's national cybersecurity watchdog, CERT-In, pointed to cracks in two widely used products: Google Chrome and GitLab. Reported on October 30, 2025, the warning asks people and administrators to act now, because a flaw in a browser can be reached by something as ordinary as a web page someone happens to open. The advisory points toward the remedy as well, linking the vendors' own updates, a reminder that trust in the tools we use is kept not by perfection but by the steady, unglamorous work of mending what is found.
India's national cybersecurity watchdog, CERT-In, has issued a warning to people who use Google Chrome and to those who run GitLab. Both products contain flaws the agency considers serious enough to demand fixes now. The advisory, reported on October 30, 2025, describes weaknesses in several parts of Chrome, including its V8 component and App-Bound encryption feature.
The central concern is how easily an attacker could reach a victim. A remote attacker could exploit the Chrome flaws through specially crafted web pages, which means a person might not need to install anything suspicious at all. Visiting a page built to trigger the flaw could be enough. Exploitation could allow arbitrary code to run on the affected machine and bypass the browser's protections, a threat CERT-In framed as serious for user privacy.
The GitLab problem is different in kind. CERT-In found improper access control on GitLab platforms, meaning the system does not adequately restrict who can reach certain resources, and data disclosure is listed among the risks.
The advisory also points toward a way forward, supplying update links from Google and GitLab and urging immediate installation of the released patches. The coverage does not provide CVE identifiers, severity scores, specific affected versions, or any confirmation of exploitation in the wild, so administrators will need to consult the advisory and vendor notices for those details. For now, the guidance is clear: apply the linked updates promptly.
India's national cybersecurity watchdog has put out a warning for people who use Google Chrome or run GitLab: both products contain flaws serious enough that the agency wants them fixed now. The Indian Computer Emergency Response Team, known as CERT-In, flagged the problems in an advisory reported on October 30, 2025.
The Chrome issues sit in several parts of the browser, including its V8 component and its App-Bound encryption feature. According to the report, the weaknesses are rooted in those elements and in others the coverage does not list.
CERT-In's concern is how an attacker might reach a victim. The agency warned that a remote attacker could exploit the Chrome flaws using specially crafted web pages. The practical meaning is that a person would not need to install anything suspicious. A page built to trigger the flaw could be enough to start the attack.
The consequences the agency describes are substantial. Exploitation could let an attacker execute arbitrary code on the affected machine and get around the security limitations the browser is meant to enforce. CERT-In framed this as a significant threat to user privacy, and the broader warning covers data theft and other attacks.
The GitLab problem is of a different kind. On GitLab platforms, CERT-In identified unauthorized access resulting from improper access control. In plain terms, the system does not adequately restrict who can reach certain things, so someone who should be shut out might get in. The report also lists data disclosure among the risks attached to these flaws.
The advisory does not stop at diagnosis. CERT-In has supplied update links from both Google and GitLab, pointing users to the vendors' own fixes. The agency urged immediate action to protect systems, which means installing the released patches rather than waiting.
The coverage leaves some things out. It does not give CVE identifiers, severity scores, or the specific Chrome and GitLab versions affected, and it does not say whether any of the flaws are being exploited in the wild. Readers who manage systems will want to consult the advisory and vendor notices directly for those details.
For now, the instruction is simple. Individual Chrome users and administrators of GitLab installations should apply the vendor updates CERT-In has linked, since the Chrome flaws in particular can be reached through nothing more than a malicious web page.
Citations marquantes
Remote attackers could exploit the Chrome flaws through specially crafted web pages, potentially executing arbitrary code and bypassing security limitations.— CERT-In advisory, as reported by Devdiscourse
Envie de l'histoire complète ?
Lire l'original sur Devdiscourse ↗
Technology