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, 0 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.
tldr: the live version is here: https://curl.se/perf/ How fast is “fast” and is it good enough? Does it run as fast now as it did before or was there a regression? What exactly needs to be fast? How fast is it? These are questions that many projects and products face, and in curl we are … Continue reading curl performance →
First reported Aug 14, 2026 11:20 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordThis afternoon I had a meeting with IT people at a huge US power infrastructure company. They had found a libcurl.dll file in their C:\Windows\System32 directory and asked us for help to upgrade it. Their vulnerability scanner identified it as vulnerable to several publicly known vulnerabilities. Can we bump it to the latest version please? … Continue reading There’s a libcurl.dll in my system32 →
First reported Aug 17, 2026 21:27 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordOn October 14 2026 we will ship curl 8.23.0. The next iteration in the never-ending series of version bumps from the curl project. We always think of the next release as the best version we ever did – and this time is no exception. Decades of collected experiences and meticulous polishing has lead us to … Continue reading Twenty-two pending curl vulnerabilities →
First reported Oct 07, 2026 07:12 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordSee also: day one, day two. There is only one thing that is better than two days of HTTP workshop, and that is of course three days of HTTP workshop. The final day of this edition of the series started out with us again shuffling around where we parked ourselves around the big table. Except … Continue reading Workshop Basel day three →
First reported Jul 16, 2026 20:01 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordWelcome to this new release. Get it as always from https://curl.se. If you rather want a security-patched older release branch, stay tuned for the follow-up Rock-solid curl announcement within a few days. Release presentation Numbers the 276th release6 changes70 days (total: 10,887)302 bugfixes (total: 14,489)525 commits (total: 39,608)0 new public libcurl function (total: 100)4 new … Continue reading curl 8.22.0 →
First reported Sep 02, 2026 05:52 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordIt takes a village to make curl. A rather big village. I have not been a solo maintainer of curl for a long time and I don’t even do half of the commits anymore Since today, the curl git repository holds the accumulated efforts from 1,500 separate and named individuals. Only 4.5 years since we … Continue reading 1,500 curl authors →
First reported Jul 25, 2026 14:29 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordThe recently published RFC 9421 describes how to do HTTP Message Signatures, and starting just now, curl experimentally supports them. Message Signatures The specification describes this as a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. It is a way to verify that selected parts … Continue reading HTTP Message Signatures with curl →
First reported Jul 27, 2026 06:55 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordExactly on this day, September 25 2001, Apple shipped version 10.1 of their OS X operating system. The one they later would rename to macOS. Exactly twenty-five years ago today. Within all their fancy release presentations and videos there are barely no mentions of curl. In their technical notes page, there is just this short … Continue reading 25 years on Apple computers →
First reported Sep 25, 2026 07:57 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordAt this exact moment curl’s summer of bliss 2026 ends. We (the maintainers of curl) took the entire month of July off from vulnerability reporting and in this post I will try to explain how this went. (If you feel like skipping the wordy blab below, the single word answer is: fine) This was possibly … Continue reading What the bliss taught us →
First reported Aug 03, 2026 06:42 UTCCatalog metadata updated Oct 13, 2026 06:03 UTCOpen evidence recordA CVSS score 3.3 AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N severity vulnerability discovered by 'NURIHAN KIM (HanTul)' was reported to the affected vendor on: 2026-10-01, 12 days ago. The vendor is given until 2027-01-29 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Oct 01, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H severity vulnerability discovered by 'Anonymous' was reported to the affected vendor on: 2026-08-25, 49 days ago. The vendor is given until 2026-12-23 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Aug 25, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 3.3 AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N severity vulnerability discovered by 'NURIHAN KIM (HanTul)' was reported to the affected vendor on: 2026-09-10, 33 days ago. The vendor is given until 2027-01-08 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 10, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 3.3 AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N severity vulnerability discovered by 'Liang Zhu' was reported to the affected vendor on: 2026-08-21, 53 days ago. The vendor is given until 2026-12-19 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Aug 21, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H severity vulnerability discovered by 'Anonymous' was reported to the affected vendor on: 2026-09-28, 15 days ago. The vendor is given until 2027-01-26 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 28, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 9.0 AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H severity vulnerability discovered by 'msh1307' was reported to the affected vendor on: 2026-09-22, 21 days ago. The vendor is given until 2027-01-20 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 22, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H severity vulnerability discovered by 'Aaron Luo and Ziv Chang of VicOne LAB R7' was reported to the affected vendor on: 2026-09-11, 32 days ago. The vendor is given until 2027-01-09 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 11, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H severity vulnerability discovered by 'Brandon Evans of TrendAI Zero Day Initiative' was reported to the affected vendor on: 2026-10-01, 12 days ago. The vendor is given until 2027-01-29 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Oct 01, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 6.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L severity vulnerability discovered by 'WONJOON HWANG (@joon1337)' was reported to the affected vendor on: 2026-09-02, 41 days ago. The vendor is given until 2026-12-31 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 02, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H severity vulnerability discovered by 'Ziyu Lin (Nanyang Technological University)' was reported to the affected vendor on: 2026-10-02, 11 days ago. The vendor is given until 2027-01-30 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Oct 02, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 5.9 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N severity vulnerability discovered by 'Anas Almizani (@x6vrn)' was reported to the affected vendor on: 2026-09-09, 34 days ago. The vendor is given until 2027-01-07 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 09, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 4.4 AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L severity vulnerability discovered by '4nibhal' was reported to the affected vendor on: 2026-09-02, 41 days ago. The vendor is given until 2026-12-31 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 02, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 4.9 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N severity vulnerability discovered by 'Anonymous' was reported to the affected vendor on: 2026-09-03, 40 days ago. The vendor is given until 2027-01-01 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 03, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 5.0 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N severity vulnerability discovered by 'p0her (@_p0her_) of TeamH4C' was reported to the affected vendor on: 2026-09-09, 34 days ago. The vendor is given until 2027-01-07 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 09, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 UTCOpen evidence recordA CVSS score 7.8 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H severity vulnerability discovered by 'ub1cu0' was reported to the affected vendor on: 2026-09-24, 19 days ago. The vendor is given until 2027-01-22 to publish a fix or workaround. Once the vendor has created and tested a patch we will coordinate the release of a public advisory.
First reported Sep 24, 2026 05:00 UTCCatalog metadata updated Oct 13, 2026 05:49 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.