Published file metadata, source observations, indicators, and research history in one bounded catalog.
Sources represented on this page. Publication and observation dates describe the content; successful batch dates describe local collection. A recent batch does not certify complete coverage or current provider availability.
2 sources: 0 stale, 0 needing attention, 0 paused, 2 unverified.
Stale means older than twice the recorded collection interval, with a minimum of one hour; without an interval, the threshold is 24 hours. Cached content remains available while a feed is stale, paused, or unverified.
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordSecurity Updates table updated provide links to the KB articles and download center updates. Microsoft recommends installing the updates.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThis CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see [Google Chrome Releases](https://chromereleases.googleblog.com/2026) for more information.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordSecurity Updates table updated provide links to the KB articles and download center updates. Microsoft recommends installing the updates.
First reported Sep 25, 2026 14:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordWe’re excited that Squarespace has decided to protect the millions of sites they host with HTTPS! While talking with their team we learned they were deploying OCSP Stapling from the get-go, and we were impressed. We asked them to share their experience with our readers in our first guest blog post (hopefully more to come). - Josh Aas, Executive Director, ISRG / Let’s Encrypt OCSP stapling is an al
First reported Oct 24, 2016 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordLet’s Encrypt has reached a milestone: we’ve now issued more than 100,000,000 certificates. This number reflects at least a few things: First, it illustrates the strong demand for our services. We’d like to thank all of the sysadmins, web developers, and everyone else managing servers for prioritizing protecting your visitors with HTTPS. Second, it illustrates our ability to scale. I’m incredibly
First reported Jun 28, 2017 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordOur goal with Let’s Encrypt is to get the Web to 100% HTTPS. We’d like to give a quick progress update. Let’s Encrypt has issued more than 5 million certificates in total since we launched to the general public on December 3, 2015. Approximately 3.8 million of those are active, meaning unexpired and unrevoked. Our active certificates cover more than 7 million unique domains. A couple of different
First reported Jun 22, 2016 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordIt has long been a dream of ours for there to be a standardized protocol for certificate issuance and management. That dream has become a reality now that the IETF has standardized the ACME protocol as RFC 8555. I’d like to thank everyone involved in that effort, including Let’s Encrypt staff and other IETF contributors. Having a standardized protocol for certificate issuance and management is imp
First reported Mar 11, 2019 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordUpdate, March 13, 2018 Wildcard certificate support is live. Let’s Encrypt will begin issuing wildcard certificates in January of 2018. Wildcard certificates are a commonly requested feature and we understand that there are some use cases where they make HTTPS deployment easier. Our hope is that offering wildcards will help to accelerate the Web’s progress towards 100% HTTPS. Let’s Encrypt is curr
First reported Jul 06, 2017 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordAs of the end of July 2018, the Let’s Encrypt root, ISRG Root X1, is directly trusted by Microsoft products. Our root is now trusted by all major root programs, including Microsoft, Google, Apple, Mozilla, Oracle, and Blackberry. Today’s announcement that we’re trusted by all major root programs represents a major milestone for us, but it’s not the conclusion of our journey towards being directly
First reported Aug 06, 2018 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordWe’re pleased to announce that OVH has renewed their support for Let’s Encrypt as a Platinum sponsor for the next three years. OVH’s strong support for Let’s Encrypt will go a long way towards creating a more secure and privacy-respecting Web. OVH initially got in touch with Let’s Encrypt to become a Platinum sponsor shortly after our public launch in December of 2015. It was clear that they under
First reported Mar 23, 2017 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordLet’s Encrypt is leaving beta today. We’re also excited to announce that founding sponsors Cisco and Akamai have renewed their Platinum sponsorships with 3-year commitments, Gemalto is joining as our newest Gold sponsor, and HP Enterprise, Fastly, Duda and ReliableSite.net are our newest Silver sponsors. Since our beta began in September 2015 we’ve issued more than 1.7 million certificates for mor
First reported Apr 12, 2016 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordLet’s Encrypt is happy to announce full support for IPv6. As IPv4 address space is exhausted, more and more people are deploying services that are only reachable via IPv6. Adding full support for IPv6 allows us to serve more people and organizations, which is important if we’re going to encrypt the entire Web. IPv6 is an exciting step forward which will allow the Internet to grow and reach more pe
First reported Jul 26, 2016 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordFile hash published by the cited source.
First reported Apr 04, 2018 16:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordLet’s Encrypt recently launched SCT embedding in certificates. This feature allows browsers to check that a certificate was submitted to a Certificate Transparency log. As part of the launch, we did a thorough review that the encoding of Signed Certificate Timestamps (SCTs) in our certificates matches the relevant specifications. In this post, I’ll dive into the details. You’ll learn more about X.
First reported Apr 04, 2018 16:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordLet’s Encrypt is pleased to introduce support for issuing certificates that contain Internationalized Domain Names (IDNs). This means that our users around the world can now get free Let’s Encrypt certificates for domains containing characters outside of the ASCII set, which is built primarily for the English language. We’re excited about this feature because our goal is to serve the entire Web, i
First reported Oct 21, 2016 00:00 UTCCatalog metadata updated Oct 08, 2026 03:55 UTCOpen evidence recordThe public shared-host view reaches the newest 2,400 matching records. Narrow the filters or search an exact MD5, SHA-1, or SHA-256 value to reach a specific record.
A filename, label, or report mention alone does not establish maliciousness. Observation dates describe cited sources; collection dates describe this local metadata catalog. No malware samples are stored, fetched, or executed by these pages.