[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-71882":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":25,"hasPages":23,"topics":26,"createdAt":10,"pushedAt":10,"updatedAt":43,"readmeContent":44,"aiSummary":45,"trendingCount":16,"starSnapshotCount":16,"syncStatus":46,"lastSyncTime":47,"discoverSource":48},71882,"cve","trickest\u002Fcve","trickest","Gather and update all available and newest CVEs with their PoC.","https:\u002F\u002Ftrickest.com",null,"HTML",7865,970,392,15,0,8,41,114,24,39.96,"MIT License",false,"main",true,[5,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"cve-poc","exploit","hacking","infosec","latest-cve","penetration-testing","pentesting","poc","red-team","security","security-tools","software-security","software-vulnerabilities","software-vulnerability","vulnerabilities","vulnerability","2026-06-12 02:02:55","\u003Ch1 align=\"center\">CVE PoC \u003Ca href=\"https:\u002F\u002Ftwitter.com\u002Fintent\u002Ftweet?text=CVE%20PoC%20-%20Find%20almost%20every%20publicly%20available%20CVE%20Proof-of-Concept%2E%0Aby%20%40trick3st%0Ahttps%3A%2F%2Fgithub%2Ecom%2Ftrickest%2Fcve%0A&hashtags=cve,poc,vulnerability,vulnerabilities,exploit,infosec,cybersecurity\">\u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FTweet--lightgrey?logo=twitter&style=social\" alt=\"Tweet\" height=\"20\"\u002F>\u003C\u002Fa>\u003C\u002Fh1>\n\u003Ch3 align=\"center\">Almost every publicly available CVE PoC.\u003C\u002Fh3>\n\n## Current hottest CVEs\n| Title      | URL |  \n| ----------- | ----------- |  \n| CVE-2022-0001      | [\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-0001.md](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-0001.md) |  \n| CVE-2022-25297      | [\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-25297.md](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-25297.md) |  \n| CVE-2022-1388      | [\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-1388.md](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-1388.md) |  \n| CVE-2022-25451      | [\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-25451.md](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fblob\u002Fmain\u002F2022\u002FCVE-2022-25451.md) |  \n\nTo see the complete history go [here](hot_cves.csv)\n\n[\u003Cimg src=\".\u002Fbanner.png\" \u002F>](https:\u002F\u002Ftrickest.io\u002Fauth\u002Fregister)\n\n## How it works\n### [Trickest](https:\u002F\u002Ftrickest.com) Workflow Architecture\n\n![Trickest Workflow - PoC](workflow.png \"Trickest Workflow - PoC\")\n\n### TB; DZ (Too big; didn't zoom):\n- Collect CVE details from [cvelist](https:\u002F\u002Fgithub.com\u002FCVEProject\u002Fcvelist) (Shout out to [CVE Project](https:\u002F\u002Fgithub.com\u002FCVEProject)!)\n- Split CVEs up by year.\n- Find PoCs for each CVE using 2 techniques:\n    1. References\n        - Gather each CVE's `References`.\n        - Check if any of them points to a PoC using [ffuf](https:\u002F\u002Fgithub.com\u002Fffuf\u002Fffuf) and a list of keywords\n\n         Regex:\n         ```(?i)[^a-z0-9]+(poc|proof of concept|proof[-_]of[-_]concept)[^a-z0-9]+```\n\n         (Thanks [@joohoi](https:\u002F\u002Fgithub.com\u002Fjoohoi)!)\n         \n         **Note**: [ffuf](https:\u002F\u002Fgithub.com\u002Fffuf\u002Fffuf) is awesome for more purposes than just content discovery.\n\n         Get CVE referenced in HackerOne Reports - [AllVideoPocsFromHackerOne](https:\u002F\u002Fgithub.com\u002Fzeroc00I\u002FAllVideoPocsFromHackerOne) (Thanks [@zeroc00I](https:\u002F\u002Fgithub.com\u002Fzeroc00I)!)\n\n\n    2. Github\n        \n        Search GitHub for repositories with [find-gh-poc](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Ffind-gh-poc) that mention the CVE ID.\n- Merge the fresh results into the repository without overwriting the data that was committed manually.\n- Filter false positives using `blacklist.txt`.\n- Merge all of the found PoCs.\n- Generate GitHub badges for each affected software version using [shields.io](https:\u002F\u002Fshields.io).\n- Write everything into easy-to-read markdown files.\n\n\n\n> **As described, almost everything in this repository is generated automatically. We carefully designed the workflow (and continue to develop it) to ensure the results are as accurate as possible.**\n\n\n\n## Use cases \n- Browse around, find a nice PoC, and test away!\n- `Watch` the repository to receive notifications about new PoCs as soon as they go public.\n- Search for a specific product(s) (and possibly version) to find all public exploits related to it.\n- Monitor the [atom feed](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fcommits\u002Fmain.atom) for a specific product(s).\n- Create a searchable HTML table using the template and script in [summary_html](summary_html)\n    - Example: https:\u002F\u002Fwww.andrewmohawk.com\u002Fcve_summary (Thanks [@AndrewMohawk](https:\u002F\u002Fgithub.com\u002FAndrewMohawk)!)\n\n## Contribution\nAll contribtutions\u002Fideas\u002Fsuggestions are welcome! Create a new ticket via [GitHub issues](https:\u002F\u002Fgithub.com\u002Ftrickest\u002Fcve\u002Fissues) or tweet at us [@trick3st](https:\u002F\u002Ftwitter.com\u002Ftrick3st).\n\n## Build your own workflows\n\nWe believe in the value of tinkering; cookie-cutter solutions rarely cut it. Sign up for a [Trickest](https:\u002F\u002Ftrickest.com) demo to customize this workflow to your use case, get access to many more workflows, or build your own workflows from scratch!\n\n[\u003Cimg src=\".\u002Fbanner.png\" \u002F>](https:\u002F\u002Ftrickest.io\u002Fauth\u002Fregister)\n","trickest\u002Fcve 项目致力于收集和更新所有可用的最新CVE（Common Vulnerabilities and Exposures）及其对应的PoC（Proof of Concept）。其核心功能包括自动从多个来源抓取CVE信息，并通过参考链接和GitHub搜索技术寻找相关PoC，同时利用ffuf等工具过滤出有效的PoC。该项目还提供了详细的文档和易于阅读的Markdown文件来展示这些漏洞详情。适用于信息安全专业人士、渗透测试人员以及红队成员进行漏洞研究与验证工作。",2,"2026-06-11 03:39:03","high_star"]