Both are rated 9.8 and need no login: one runs commands as root on Session Smart Conductor, the other hands admin rights on routers not yet onboarded. Fixed in 7.0.5, 7.1.7 and 7.2.3; Juniper says no workaround exists.
Hijacked .gh, .sl and .as domains used to get fake Google certificates
EditorialBy TrustList Editorial
Chrome users are protected automatically, but other browsers and apps may not be. Google urges domain owners to watch certificate logs and restrict which certificate authorities may issue for them.
- Cybersecurity
- Vulnerability Management
- Ghana
- American Samoa
- +1 more
About Hijacked .gh, .sl and .as domains used to get fake Google certificates
Hijacked .gh, .sl and .as domains used to get fake Google certificates
6 October 2026: Attackers who took over three country-code top-level domain registries, .gh for Ghana, .sl for Sierra Leone and .as for American Samoa, used that control to obtain unauthorised HTTPS certificates for Google properties and for other organisations' domains. Google's Chrome team says it has blocked the certificates it found and that Chrome users need to do nothing. The company says the attacks did not compromise Google's own systems: the target was the registries.
Not yet independently verified. Google does not name the other affected organisations or say how many certificates were issued, and says it cannot guarantee it found every affected domain. The Ars Technica page could not be read by us, so it is cited from its headline only. We will update this when it can be confirmed, and remove this note.
A certificate authority normally issues a certificate once the applicant proves control of a domain, typically through a DNS record. Because the attackers had altered DNS records at the registry level, they could pass that check. Google responded by pushing the certificates covering its own services into CRLSets, the list Chrome uses to block specific certificates without waiting for slower revocation checks, and by asking the issuing certificate authorities to revoke them. It then searched Certificate Transparency logs, found further certificates tied to other organisations, and blocked those in Chrome too.
Google states two limits. Its analysis may not have identified every affected domain, and Chrome's protection does not extend to other clients. Browsers and apps that do not read CRLSets depend on formal revocation by the issuing authority.
The post sets out three steps for domain owners:
- monitor Certificate Transparency logs across the whole domain portfolio, including regional and parked domains, to catch certificates nobody requested
- publish restrictive CAA records, with ACME account bindings where possible, so only the authorities you use can issue for your names
- remember that authorities may reuse an earlier domain validation, so an attacker who passed a check during the hijack may still obtain certificates after DNS control is restored
For the longer term, Google says it will work through the Chrome Root Program to shorten certificate lifetimes and limit how long a validation can be reused.
Related on TrustList:
- HPE fixes 37 flaws in AOS-Switch and ClearPass Policy Manager
- Juniper fixes two critical root flaws in Session Smart Router
Sources
Categories & features
- Cybersecurity
- Vulnerability Management
- Ghana
- American Samoa
- Networking
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
Sixteen are rated critical and 12 high. Italy's national cyber agency lists remote code execution and authentication bypass among the flaw types and records no public exploit or exploitation.
The ten-year contract starts on 3 May 2027 and covers the MPLS and SD-WAN network, API integration, digital identity and a security operations centre linking the ECB with banks, fintechs and payment providers. No value was stated.
Juniper's October bulletin JSA112187 fixes nine Junos OS and Junos OS Evolved flaws rated CVSS 9.8, in BGP flowspec and BMP handling, EVPN-VPWS, J-Web and httpd, with fixed releases across seven trains.
Seven CVE records scored 10.0 cover authentication bypass, command injection, SQL injection and buffer overflows that need no login. Fixed releases are 10.8.1.2, 10.7.2.7, 10.4.1.14, 8.13.3.1 and 8.10.0.24.
IBM's records cover Langflow OSS 1.0.0 to 1.12.8: an authentication bypass and code execution, both 9.8 with no login needed. Version 1.12.8, released hours before the fix, is still affected.
A client with no credentials can tie up memory, file descriptors and backend connections on Traefik 3.7.14 to 3.7.16 and 2.11.58 to 2.11.60, whether or not NTLM is used. It is the latest of more than a dozen fixes since 6 October.
The IDEs ship their own Java runtime and trust store, so an operating system update does not remove the eight compromised intermediates. Fixes run from 2026.2.4 and Toolbox 3.9.1; 2025.1 and older get none.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.