
🧪 Collects CVE PoCs and backs them up to the Internet Archive when they are unavailable on GitHub.
Poc CVE Collection
🧪 Collects CVE PoCs and backs them up to the Internet Archive when they are unavailable on GitHub.
|
Support the maintenance of this project with PayPal or by scanning the QR code. Your donation helps me search GitHub for missing CVE proof-of-concept repositories, verify and organize new findings, preserve unavailable repositories through the Internet Archive, and keep this collection useful and up to date for everyone. Donate to help me find and archive missing CVE resources for you and the wider security community. Every contribution supports the time and infrastructure needed for continuous discovery, backup, and maintenance.
|
Scan with ABA Mobile · Click to enlarge View donation records and images → |
Archives use OpenSSL AES-256-CBC with PBKDF2. Build the password by joining
these values with _, then append the CVE ID:
PASSWORD_SUFFIX = learn_coding_is_rean-it.com_IlovefamilyHKimhab
PASSWORD_PUBLIC3SEP26 = Ilovemyandwifefamily_AmazingCambodia_Iamaspeckintheuniverse_bluedot_passwordgenerator.rean-it.com$$$
SECRET_KEY_REAN_IT = "rean-it.com..."
Password = PASSWORD_SUFFIX_PASSWORD_PUBLIC3SEP26<SECRET_KEY_REAN_IT><CVE-ID>
Example for CVE-2026-31431:
openssl enc -d -aes-256-cbc -pbkdf2 \
-in "${FILE}" -out "${CVE_ID}.zip" -pass "pass:${PASSWORD}"
unzip "${CVE_ID}.zip" -d "${CVE_ID}"
Replace FILE with the downloaded filename. Keep the fixed password text in
single quotes so the shell does not expand $$.
# CVE-2026-31431
# Title
crypto: algif_aead - Revert to operating out-of-place
# Description
In the Linux kernel, the following vulnerability has been resolved: crypto: algif_aead - Revert to operating out-of-place This mostly reverts commit 72548b093ee3 except for the copying of the associated data. There is no benefit in operating in-place in algif_aead since the source and destination come from different mappings. Get rid of all the complexity added for in-place operation and just copy the AD directly.
# POCs
- https://github.com/theori-io/copy-fail-CVE-2026-31431
- https://github.com/rootsecdev/cve_2026_31431
- https://github.com/badsectorlabs/copyfail-go
# Backup pocs
- https://archive.org/details/cve-2026-31431-2026-07-15-1784090663.zip
The poc-cve-collection-script/pocs-list.json file is stored with Git LFS so
it can grow beyond GitHub's regular Git file-size limits. Install Git LFS before
cloning or updating the repositories:
git lfs install
git clone --recurse-submodules https://github.com/HORKimhab/poc-cve-collection.git
git -C poc-cve-collection-script lfs pull
When migrating an existing checkout, commit and push the LFS change in the submodule first, then commit and push the updated submodule pointer in this repository. GitHub Actions performs the LFS setup and download automatically.
GitHub repositories whose names do not explicitly identify the CVE being
processed are kept out of the confirmed CVE record. They are stored by the
searched CVE year using the existing repoName-authorName convention:
2026/unknown/repository-name-owner.md
Each unknown record contains the repository name, every CVE search that found it, its GitHub PoC URL, and any backup PoC URLs. Unknown repositories continue through the clone and archive pipeline so they can still be preserved. For example:
# repository-name
## Discovered While Searching
- CVE-2026-36214
## POCs
- https://github.com/owner/repository-name
## Backup pocs
retry in 6 attemps, 1, 3, 9, 11, 15