{
  "id": 16052205,
  "title": "Leaked private keys for eight CA certificates let any attacker impersonate any domain",
  "url": "https://urgent.news/2026/10/22/leaked-private-keys-for-eight-ca-certificates-let-any-attacker",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-22T13:14:20.000Z",
  "source": {
    "name": "Tom's Hardware",
    "slug": "tom-s-hardware",
    "url": "https://www.tomshardware.com/tech-industry/cyber-security/leaked-private-keys-for-eight-ca-certificates-let-any-attacker-impersonate-any-domain-billions-of-older-devices-and-software-installations-may-be-vulnerable-after-round-of-fixes-patch-yours-immediately"
  },
  "original_language": "en",
  "account": "This week has been particularly challenging for systems administrators worldwide, as they face the need to update numerous machines and software due to eight insecure intermediate CA certificates. These certificates, issued by Indian CA firm eMudhra, can enable attackers to impersonate any domain and make malware appear legitimate. An attacker positioned along a network's path, such as in a company or government network, public Wi-Fi, or the ISP, can intercept connections and pose as reputable websites like apple.com, amazon.com, or bankofamerica.com. If left unaddressed, operating systems and installed software would remain unaware of the threat.\n\nThe code signing certificates further exacerbate the issue, as applications downloaded from seemingly legitimate sources, such as Microsoft or Google, could be displayed as genuine. Software checks a certificate's legitimacy by verifying its chain, which involves a certificate issued and signed by an intermediate Certification Authority and its certificate being trusted and signed by root certificates. The keys for these root certificates are typically kept offline in secure safes.\n\nThe eMudhra incident involved the issuance of six TLS and two code-signing intermediate certificates with easily guessable keys, leaving operating systems and numerous applications with trust lists that need updating. These trust lists are periodically updated to address screw-ups, like the one experienced this week. To resolve the issue, administrators must revoke the eight CAs, remove the affected root certificate, or hard-code a rejection of all eight affected keys.\n\nFortunately, recent versions of Chrome, Brave, Firefox, and Safari implement Certificate Transparency, a feature that consults a public read-only log of certificate issuances and blocks certificates not mentioned in the log. However, users must still ensure their software is updated. The problem lies in the sheer number of devices and software requiring updates, including PCs, servers, operating systems, phones, tablets, routers, web browsers, applications, virtual servers, virtual machines, containers, programming languages, standalone download utilities, and potentially more. Old routers, smart and IoT appliances, and outdated computers could also pose issues in the future.\n\nWhile the exact cause of the weak private keys remains under investigation, the incident highlights the importance of regularly updating systems and software to protect against potential security threats.",
  "summary": "Leaked private keys for eight CA certificates let any attacker impersonate any domain — billions of older devices and software installations may be vulnerable after round of fixes, patch yours immediately",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}