curl to handle low- and medium-risk vulnerability reports publicly on GitHub from Oct 26
The curl project is changing its vulnerability disclosure process so that, from October 26, reports judged low or medium risk will be filed and discussed publicly in GitHub Issues, while high-risk and critical issues continue to be handled privately through HackerOne. Maintainer Daniel Stenberg said the steady influx of reports is overloading the maintenance team, and the new policy lets outside developers help confirm issues, check fixes and write security advisories; researchers unsure of severity can still submit to HackerOne, but low or moderate cases will be redirected to GitHub and the original report closed as informational. Stenberg said more than ninety percent of reports received in recent years could quickly be judged below high risk even though checking each still consumed substantial effort, and that many recent findings came from researchers using AI models to test libcurl options, protocols and operation sequences, with some anomalies appearing only in rarely used combinations that he considers unlikely to affect users.
curl is used both as a command-line tool and as the libcurl library inside other software, and the project says public review may let more people check whether fixes are complete and find similar flaws before a release, while limiting the change to lower-risk cases because early disclosure of unpatched flaws could give attackers more time.
文/李建興|2026-10-21 發表
開源網路傳輸工具curl專案**調整漏洞揭露程序**,10月26日起經團隊判定為低或中度風險的漏洞,將改在GitHub Issues公開通報與討論,高風險及重大漏洞則繼續透過HackerOne私下處理。curl主要維護者Daniel Stenberg指出,持續湧入的漏洞報告讓維護團隊難以負荷,希望藉由公開處理分攤工作。
curl除了提供命令列工具,也透過libcurl函式庫供其他軟體傳輸網路資料。原本安全漏洞須先私下通報,由維護團隊確認、修補後再公開,新政策則讓外部開發者參與中低風險漏洞的問題確認、修補檢查及安全公告撰寫。研究人員若不確定漏洞嚴重程度,仍可先提交HackerOne,要是curl判定為低或中度風險,便會要求改在GitHub提出,原本的HackerOne通報會註記為資訊性案件後結案,並公開內容。
Daniel Stenberg表示,過去幾年收到的通報,超過九成可迅速判定未達高風險,但逐件檢查仍耗費大量人力。近來不少漏洞是研究人員利用AI模型測試libcurl各種選項、網路協定及操作順序後找出。有些異常只在實務上極少使用的操作組合下出現,另一些則是每次採用相關操作組合都會出現異常,開發者容易察覺,他認為,這類問題實際影響使用者的機會很低。