REPO STARS
RELEASED
NAME
DESCRIPTION
0 ★php2shellCVE-2026-109618 detailsPHP2Shell - CVE-2026-109618/109619 session.upload_progress UAF PoC - multi-target RCE chain - created by 0verDo$ed
1 ★CVE-2026-109618_CVE-2026-109619CVE-2026-109618 detailsPoC for PHP2Shell (CVE-2026-109618 / CVE-2026-109619) zero-depndency, pre-auth RCE via a use-after-free in PHP's session.upload_progress handler. Affects PHP 5.48.5.11 fixed in 8.2.35+
0 ★novel-php2shellCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
0 ★php2shell-CVE-2026-109618-109619CVE-2026-109618 detailsFull 1:1 reproduction of php2shell (CVE-2026-109618 / CVE-2026-109619): pre-auth PHP RCE via session.upload_progress OOM corruption and stale cross-request state. Pinned mod_php 8.4.26 / Apache 2.4.69 aarch64 lab, pure HTTP, heap-layout ASLR bypass, no brute force.
0 ★CVE-2026-109618-and-CVE-2026-109619-ExploitCVE-2026-109618 detailsCVE-2026-109618 and CVE-2026-109619 exploit
1 ★Gitlab-RCE-CVE-2026-110264CVE-2026-110264 detailsCVE-2026-110264: GitLab Unauthenticated RCE via Onigmo Regex Integer Overflow
0 ★AiDot-SSDP-UPnP-VulnerabilitiesCVE-2026-78845 detailsPublic proof-of-concept links are available. Official CVE details are pending.
0 ★CVE-2026-111497-POCCVE-2026-111497 detailsReproducible local Brotli decoder proof for CVE-2026-111497 with a self-checking tuned RCE harness
2 ★php2shellCVE-2026-109618 detailsCVE-2026-109618 / CVE-2026-109619 PHP PoC and exploit tool (single-file Go)
0 ★php2shell-pocCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
0 ★php2shellCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
1 ★KEVCVE-2025-14847-pocCVE-2025-14847 detailsMismatched length fields in Zlib compressed protocol headers may allow a read of uninitialized heap memory by an unauthenticated client. This issue affects all MongoDB Server v7.0 prior to 7.0.28 versions, MongoDB Server v8.0 versions prior to 8.0.17, MongoDB Server v8.2 versions prior to 8.2.3, MongoDB Server v6.0 versions prior to 6.0.27, MongoDB Server v5.0 versions prior to 5.0.32, MongoDB Server v4.4 versions prior to 4.4.30, MongoDB Server v4.2 versions greater than or equal to 4.2.0, MongoDB Server v4.0 versions greater than or equal to 4.0.0, and MongoDB Server v3.6 versions greater than or equal to 3.6.0.
2 ★php2shell-pocsCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
0 ★20261022-research-php-cveCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
1 ★php2shell-CVE-2026-109618-CVE-2026-109619-PoCCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
0 ★php2shellCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
1 ★php2shell-response-inspectorCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
1 ★php2shellCVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
2 ★php2shell-cve-2026-109618-cve-2026-109619CVE-2026-109618 detailsPHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).