LIVE · cybersecurity feed
Live wire
CVE-2024-3848 · LFProjects MLflow Path Traversal Vulnerability Added To VulnCheck KEVCVE-2026-118267 · WPDataAccess Incorrect Authorization Flaw Exploited Same Day As DisclosureCVE-2026-118066 · LatePoint Improper Authentication Vulnerability Exploited On Day Of DisclosureCVE-2026-132224 · Optimizely Web Experimentation Flaw Exploited Same Day as DisclosureCVE-2026-133968 · Project-MONIA MONAI Label Path Traversal Exploited On Disclosure DateCairn AI Framework Used in Autonomous Zero-Day ExploitationAmazon: China-Linked Hackers’ AI Agents Exploited Medical Software Zero-DayCVE-2026-129975 · GnuPG Warns Critical GPGME Flaw Could Expose App Data via Malicious OpenPGP KeysCVE-2026-129448 · Hackers Exploit Critical VMware, Cisco, and Apache Flaws as Espionage Attacks EmergeCTO of ‘RansomwareHelp’ Indicted for Wire Fraud
nation-state

Attackers hijacked top-level domains, minted fake security certs for Google and other orgs

Attackers successfully hijacked several country-code top-level domains (ccTLDs) and subsequently minted fraudulent HTTPS certificates for various Google domains and those of other entities. Google confirmed it became aware of these incidents last week, specifically impacting the .gh (Ghana), .sl (Sierra Leone), and .as (American Samoa) namespaces.

ZeroDay News ·

Source: The Register — Security

Attackers successfully hijacked several country-code top-level domains (ccTLDs) and subsequently minted fraudulent HTTPS certificates for various Google domains and those of other entities. Google confirmed it became aware of these incidents last week, specifically impacting the .gh (Ghana), .sl (Sierra Leone), and .as (American Samoa) namespaces.

During these attacks, the perpetrators modified authoritative DNS records, which allowed them to obtain unauthorized HTTPS certificates. Google stated that its own systems were not compromised in the process. While Google did not specify which particular domains or organizations beyond itself were affected, it emphasized the potential for such attacks to enable impersonation without triggering standard browser security warnings.

The nature of these attacks means that an attacker could control traffic routing via DNS and possess the private key for the unauthorized certificate. This capability could allow them to intercept or modify user data intended for the legitimate site, or to leverage the trusted brand for distributing malware or conducting phishing campaigns.

Google's Chrome browser quickly implemented measures to block suspected counterfeit certificates across the affected ccTLDs, providing protection for Chrome users. However, Google cautioned domain owners against relying solely on browser-side interventions, noting that such measures might not reliably protect users of other browsers. The company also clarified that it found no indication of wrongdoing by the Certificate Authorities (CAs) that issued the impacted certificates, attributing the issue to the DNS hijacking itself.

To mitigate risks from similar attacks, Google recommends that organizations continuously monitor Certificate Transparency (CT) logs for all their domains, including parked or regional ccTLD properties. This practice provides near real-time alerts when a certificate is issued for a domain. Organizations operating domains within the .gh, .sl, or .as ccTLDs were specifically advised to review recent CT log entries for any unexpected certificates.

Additionally, Google suggests publishing restrictive Certification Authority Authorization (CAA) DNS records. These records allow domain owners to specify which CAs are authorized to issue certificates for their domains. While CAA records may not prevent certificate issuance during an active DNS hijacking, they can help secure domains once DNS control is restored. Google recommends CAA policies that limit issuance to specific authorized accounts and validation methods, thereby preventing attackers from exploiting cached validation states to mint new certificates after a hijacking concludes.

nation-state
ShareXLinkedInWhatsAppFacebook

More News

view all →
nation-state

FBI Investigating Apparent Hack of Its Key National Criminal Justice Database, AP Source Says

The Federal Bureau of Investigation is currently conducting an investigation into a potential security breach involving the National Crime Information Center, a critical repository of criminal justice data. The database, which is managed by the FBI, serves as a centralized resource for federal, state, and local law enforcement agencies. It contains sensitive information including records on…

patch

Weekly Update 531: Optimizely. Script Dependencies & Third Parties

A recent disclosure notice regarding Optimizely has highlighted ongoing concerns surrounding the security of third-party script dependencies. The incident underscores a growing trend where organizations point to external vendors when explaining security lapses, a practice that critics argue serves to deflect institutional accountability rather than addressing the underlying technical risks.

breach

Rackspace Spot breach let hackers access customer Kubernetes secrets

Rackspace has confirmed a security breach affecting its Rackspace Spot cloud platform, a service designed for managing containerized applications through Kubernetes. The unauthorized access occurred on November 17, 2026, spanning a window from approximately 00:20 to 22:00 UTC. The company discovered the intrusion on November 18 following a report from a customer and subsequently verified that…

CVE-2024-3848high

LFProjects MLflow Path Traversal Vulnerability Added To VulnCheck KEV

The LFProjects MLflow path traversal vulnerability, CVE-2024-3848, has been added to the VulnCheck KEV catalogue, 894 days after its initial publication.

CVE-2026-118267high

WPDataAccess Incorrect Authorization Flaw Exploited Same Day As Disclosure

The wp_data_access plugin for WordPress faces active exploitation following a zero-day disclosure, yet it remains absent from major federal vulnerability catalogues.

CVE-2026-118066high

LatePoint Improper Authentication Vulnerability Exploited On Day Of Disclosure

The LatePoint plugin for WordPress is currently under exploitation, with the vulnerability appearing in the VulnCheck KEV catalogue on the same day it was published.