{"vulnerability": "GHSA-X744-4WPC-V9H2", "sightings": [{"uuid": "a7209c77-2fc2-4e6c-b3fb-ea263ba7900b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "published-proof-of-concept", "source": "Telegram/84MSU-hIhNrWnS8A8cOqhlUxSHC6aqIIGr26pihaT5cA3PI", "content": "", "creation_timestamp": "2026-03-31T05:17:29.000000Z"}, {"uuid": "7f12bf11-b7c7-4151-b385-8a7475c96752", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-x744-4wpc-v9h2", "type": "seen", "source": "https://gist.github.com/cwayne18/2df919c96745d903491c33321eb89359", "content": "cwayne@geeko ~ % /System/Volumes/Data/Users/cwayne/go/bin/vexscan --image docker.io/rancher/rke2-runtime:v1.36.2-rke2r1 --all --severity CRITICAL,HIGH --vexhub https://github.com/rancher/vexhub --gist\nExtracting docker.io/rancher/rke2-runtime:v1.36.2-rke2r1 (linux/amd64)...\nScanning for Go binaries...\nFound 7 Go binaries.\nResolving advisories for 306 components (306 OSV queries)...\nVEX hub https://github.com/rancher/vexhub: 1083 products indexed\nVEX hub https://github.com/rancher/vexhub: 29 finding(s) already covered by a published statement\nvexscan report (image) for docker.io/rancher/rke2-runtime:v1.36.2-rke2r1\nNOTE: --severity CRITICAL,HIGH withheld 125 of 161 findings:\n      99 unknown (no rating was published), 24 medium, 2 low\n\n  golang   Go                        306 components    36 findings\n  affected by severity: 7 high\n  already vexed: 15 by Rancher Security team\n\nAFFECTED (7) - vulnerable code is present and can be loaded\nSEVERITY  ADVISORY      PACKAGE                 VERSION  BASIS\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.80.0\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.80.0\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.80.0\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.80.0\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.79.3\nHIGH      GO-2022-0965  k8s.io/apimachinery     (devel)\nHIGH      GO-2022-0965  k8s.io/apimachinery     (devel)\n\nALREADY VEXED (15) - a published statement answers these; vexscan's own verdict is unchanged\nSEVERITY  ADVISORY             PACKAGE                              VERSION               VEX STATUS    JUSTIFICATION\nCRITICAL  GHSA-cvxm-645q-p574  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nCRITICAL  GHSA-cvxm-645q-p574  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nCRITICAL  GHSA-cvxm-645q-p574  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-33vj-92qq-66hc  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-33vj-92qq-66hc  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-33vj-92qq-66hc  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-rgh6-rfwx-v388  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-rgh6-rfwx-v388  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-rgh6-rfwx-v388  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-xhf5-7wjv-pqxp  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-xhf5-7wjv-pqxp  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-xhf5-7wjv-pqxp  github.com/containerd/containerd/v2  v2.3.2-k3s2           not_affected  vulnerable_code_not_present\nHIGH      GHSA-x744-4wpc-v9h2  github.com/docker/docker             v27.1.1+incompatible  not_affected  vulnerable_code_not_in_execute_path\nHIGH      GO-2026-5426         go.opentelemetry.io/otel/sdk         v1.42.0               not_affected  vulnerable_code_not_in_execute_path\nHIGH      GO-2026-5426         go.opentelemetry.io/otel/sdk         v1.40.0               not_affected  vulnerable_code_not_present\n\nRULED OUT (14) - the vulnerable code is not present or cannot run\nSEVERITY  ADVISORY             PACKAGE                   VERSION               BASIS\nCRITICAL  GO-2026-5005         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5006         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5017         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5019         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5020         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5021         golang.org/x/crypto       v0.47.0               pclntab\nCRITICAL  GO-2026-5023         golang.org/x/crypto       v0.47.0               pclntab\nHIGH      GHSA-x744-4wpc-v9h2  github.com/docker/docker  v27.3.1+incompatible  pclntab-module\nHIGH      GO-2026-5617         github.com/docker/docker  v27.3.1+incompatible  pclntab\nHIGH      GO-2026-5617         github.com/docker/docker  v27.1.1+incompatible  pclntab\nHIGH      GO-2026-5746         github.com/docker/docker  v27.3.1+incompatible  pclntab\nHIGH      GO-2026-5746         github.com/docker/docker  v27.1.1+incompatible  pclntab\nHIGH      GO-2026-5013         golang.org/x/crypto       v0.47.0               pclntab\nHIGH      GO-2026-5018         golang.org/x/crypto       v0.47.0               pclntab", "creation_timestamp": "2026-08-04T15:15:12.858239Z"}, {"uuid": "1b5ad457-fe37-4688-a855-7a1780e86622", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-x744-4wpc-v9h2", "type": "seen", "source": "https://gist.github.com/cwayne18/b5c32c67446c8ec50f54ec955ba4ef5b", "content": "cwayne@geeko ~ % vexscan --image docker.io/rancher/k3s:v1.36.3-k3s1 --all --vexhub https://github.com/rancher/vexhub --severity CRITICAL,HIGH\nExtracting docker.io/rancher/k3s:v1.36.3-k3s1 (linux/amd64)...\nScanning for Go binaries...\nFound 4 Go binaries.\nResolving advisories for 457 components (457 OSV queries)...\nVEX hub https://github.com/rancher/vexhub: 1086 products indexed\nVEX hub https://github.com/rancher/vexhub: 16 finding(s) already covered by a published statement\nvexscan report (image) for docker.io/rancher/k3s:v1.36.3-k3s1\nNOTE: --severity CRITICAL,HIGH withheld 34 of 53 findings:\n      20 unknown (no rating was published), 14 medium\n\n  golang   Go                        457 components    19 findings\n  affected by severity: 3 high\n  already vexed: 5 by Rancher Security team\n\nAFFECTED (3) - vulnerable code is present and can be loaded\nSEVERITY  ADVISORY             PACKAGE                 VERSION  BASIS\nHIGH      GHSA-m4hf-6vgr-75r2  github.com/k3s-io/k3s   (devel)\nHIGH      GO-2026-6061         google.golang.org/grpc  v1.80.0\nHIGH      GO-2026-6061         google.golang.org/grpc  v1.79.3\n\nALREADY VEXED (5) - a published statement answers these; vexscan's own verdict is unchanged\nSEVERITY  ADVISORY             PACKAGE                              VERSION                       VEX STATUS    JUSTIFICATION\nCRITICAL  GHSA-cvxm-645q-p574  github.com/containerd/containerd/v2  v2.3.2-k3s2                   not_affected  vulnerable_code_not_present\nHIGH      GHSA-33vj-92qq-66hc  github.com/containerd/containerd/v2  v2.3.2-k3s2                   not_affected  vulnerable_code_not_present\nHIGH      GHSA-rgh6-rfwx-v388  github.com/containerd/containerd/v2  v2.3.2-k3s2                   not_affected  vulnerable_code_not_present\nHIGH      GHSA-xhf5-7wjv-pqxp  github.com/containerd/containerd/v2  v2.3.2-k3s2                   not_affected  vulnerable_code_not_present\nHIGH      GHSA-x744-4wpc-v9h2  github.com/docker/docker             v25.0.15-0.20260325154711-d\u2026  not_affected  vulnerable_code_not_in_execute_path\n\nRULED OUT (11) - the vulnerable code is not present or cannot run\nSEVERITY  ADVISORY      PACKAGE                   VERSION                       BASIS\nCRITICAL  GO-2026-5005  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5006  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5017  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5019  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5020  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5021  golang.org/x/crypto       v0.47.0                       pclntab\nCRITICAL  GO-2026-5023  golang.org/x/crypto       v0.47.0                       pclntab\nHIGH      GO-2026-5617  github.com/docker/docker  v25.0.15-0.20260325154711-d\u2026  pclntab\nHIGH      GO-2026-5746  github.com/docker/docker  v25.0.15-0.20260325154711-d\u2026  pclntab\nHIGH      GO-2026-5013  golang.org/x/crypto       v0.47.0                       pclntab\nHIGH      GO-2026-5018  golang.org/x/crypto       v0.47.0                       pclntab\n\nNOTE: --severity CRITICAL,HIGH withheld 34 of 53 findings:\n      20 unknown (no rating was published), 14 medium\n  golang   Go                        457 components    19 findings\n  affected by severity: 3 high\n  already vexed: 5 by Rancher Security team\n  19 findings in 3 section(s): AFFECTED (3), ALREADY VEXED (5), RULED OUT (11)", "creation_timestamp": "2026-08-05T12:34:16.634571Z"}, {"uuid": "b4820617-2808-4a53-8734-117598aea236", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-x744-4wpc-v9h2", "type": "seen", "source": "https://gist.github.com/cwayne18/f47690bfa6aef6e901eb661447319fe1", "content": "cwayne@geeko ~ % vexscan --image docker.io/rancher/k3s:v1.36.3-k3s1 --all --vexhub https://github.com/rancher/vexhub --severity CRITICAL,HIGH --llm --llm-command \"gh copilot\" --mine-advisories --triage\nLLM overlay: asking command gh\nExtracting docker.io/rancher/k3s:v1.36.3-k3s1 (linux/amd64)...\nScanning for Go binaries...\nFound 4 Go binaries.\nResolving advisories for 457 components (457 OSV queries)...\nVEX hub https://github.com/rancher/vexhub: 1090 products indexed\nVEX hub https://github.com/rancher/vexhub: 16 finding(s) already covered by a published statement\nTriaging 18 findings against EPSS and CISA KEV (16 CVE ids)\nvexscan report (image) for docker.io/rancher/k3s:v1.36.3-k3s1\nNOTE: --severity CRITICAL,HIGH withheld 34 of 52 findings:\n      21 unknown (no rating was published), 13 medium\nNOTE: --triage could not score 2 of 18 findings, so they sort last for lack of data rather than lack of risk:\n      2 carry no CVE id, which is the only key either feed has\n\n  golang   Go                        457 components    18 findings\n  affected by severity: 2 high\n  2 affected: 1 unique advisories, 2 fixable, 0 with no fix yet\n  already vexed: 5 by Rancher Security team\n  priority: none in CISA's known-exploited catalog, 0 at or above the 90th EPSS percentile, 0 scored, 2 unscored\n  priority data: EPSS 2026-08-05, KEV catalog 2026.08.05\n\nAFFECTED (2) - vulnerable code is present and can be loaded\nSEVERITY  ADVISORY      PACKAGE                 VERSION  FIXED IN  BASIS\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.80.0  1.82.1\nHIGH      GO-2026-6061  google.golang.org/grpc  v1.79.3  1.82.1\n\nALREADY VEXED (5) - a published statement answers these; vexscan's own verdict is unchanged\nSEVERITY  ADVISORY             PACKAGE                              VERSION                       FIXED IN  EPSS   VEX STATUS    JUSTIFICATION\nHIGH      GHSA-x744-4wpc-v9h2  github.com/docker/docker             v25.0.15-0.20260325154711-d\u2026  29.3.1    95.2%  not_affected  vulnerable_code_not_in_execute_path\nHIGH      GHSA-33vj-92qq-66hc  github.com/containerd/containerd/v2  v2.3.2-k3s2                   2.3.2     27.3%  not_affected  vulnerable_code_not_present\nCRITICAL  GHSA-cvxm-645q-p574  github.com/containerd/containerd/v2  v2.3.2-k3s2                   2.3.2     25.8%  not_affected  vulnerable_code_not_present\nHIGH      GHSA-rgh6-rfwx-v388  github.com/containerd/containerd/v2  v2.3.2-k3s2                   2.3.2     8.5%   not_affected  vulnerable_code_not_present\nHIGH      GHSA-xhf5-7wjv-pqxp  github.com/containerd/containerd/v2  v2.3.2-k3s2                   2.3.2     7.3%   not_affected  vulnerable_code_not_present\n\nRULED OUT (11) - the vulnerable code is not present or cannot run\nSEVERITY  ADVISORY      PACKAGE                   VERSION                       FIXED IN  EPSS   BASIS\nCRITICAL  GO-2026-5017  golang.org/x/crypto       v0.47.0                       0.52.0    46.4%  pclntab\nCRITICAL  GO-2026-5006  golang.org/x/crypto       v0.47.0                       0.52.0    45.4%  pclntab\nCRITICAL  GO-2026-5021  golang.org/x/crypto       v0.47.0                       0.52.0    43.9%  pclntab\nCRITICAL  GO-2026-5020  golang.org/x/crypto       v0.47.0                       0.52.0    41.6%  pclntab\nCRITICAL  GO-2026-5023  golang.org/x/crypto       v0.47.0                       0.52.0    40.3%  pclntab\nHIGH      GO-2026-5013  golang.org/x/crypto       v0.47.0                       0.52.0    38.4%  pclntab\nHIGH      GO-2026-5018  golang.org/x/crypto       v0.47.0                       0.52.0    38.0%  pclntab\nCRITICAL  GO-2026-5019  golang.org/x/crypto       v0.47.0                       0.52.0    34.6%  pclntab\nCRITICAL  GO-2026-5005  golang.org/x/crypto       v0.47.0                       0.52.0    33.9%  pclntab\nHIGH      GO-2026-5746  github.com/docker/docker  v25.0.15-0.20260325154711-d\u2026  no fix    5.1%   pclntab\nHIGH      GO-2026-5617  github.com/docker/docker  v25.0.15-0.20260325154711-d\u2026  no fix    1.2%   pclntab\n\nNOTE: --severity CRITICAL,HIGH withheld 34 of 52 findings:\n      21 unknown (no rating was published), 13 medium\nNOTE: --triage could not score 2 of 18 findings, so they sort last for lack of data rather than lack of risk:\n      2 carry no CVE id, which is the only key either feed has\n  golang   Go                        457 components    18 findings\n  affected by severity: 2 high\n  2 affected: 1 unique advisories, 2 fixable, 0 with no fix yet\n  already vexed: 5 by Rancher Security team\n  priority: none in CISA's known-exploited catalog, 0 at or above the 90th EPSS percentile, 0 scored, 2 unscored\n  priority data: EPSS 2026-08-05, KEV catalog 2026.08.05\n  18 findings in 3 section(s): AFFECTED (2), ALREADY VEXED (5), RULED OUT (11)", "creation_timestamp": "2026-08-05T21:55:34.220750Z"}, {"uuid": "84a9399b-3a73-48cc-a807-67ff595908cd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "seen", "source": "https://t.me/CyberSecurityExploit/31014", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-15T12:00:03.260363Z"}, {"uuid": "e4135a59-f6ec-4a74-beff-37847b271ba1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "seen", "source": "https://t.me/CyberSecurityExploit/31013", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-15T12:00:03.774496Z"}, {"uuid": "da8bfd7a-773e-430b-91f5-59d5e6c4216b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityExploit/31013", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-16T00:00:25.381258Z"}, {"uuid": "335754f1-c4b5-4515-a6ad-fc0f59e63cb5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityExploit/31014", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-16T00:00:25.640975Z"}, {"uuid": "c09dcfbb-c4d0-4b0b-bb16-14e1a3bafd5a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "published-proof-of-concept", "source": "https://t.me/CyberSecurityExploit/17189", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-28T00:00:11.837247Z"}, {"uuid": "49a2411f-570b-4a7e-a4a2-a953af0fe87a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-X744-4WPC-V9H2", "type": "seen", "source": "https://t.me/CyberSecurityExploit/17189", "content": "\u26a0\ufe0f CVE / ZERO-DAY\n\ud83d\udd25 GitHub Fresh PoC CVE TOP 5 (Today / Verified & Non-Posted Priority)\nBelow are latest 2026 CVEs with real GitHub PoC repositories (strictly validated).\n\n\u2796\u2796\u2796\u2796\n\n1\ufe0f\u20e3 CVE-2026-1668\n\ud83c\udfaf Firmware Exploit \u2013 Memory Corruption \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/tangrs/cve-2026-1668-poc\n\n\ud83e\udde0 Overview\nA firmware-level vulnerability enabling memory corruption and potential remote code execution. Active PoC confirms exploit feasibility.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Firmware compromise\n\u2022 Embedded system takeover\n\n\u2796\u2796\u2796\u2796\n\n2\ufe0f\u20e3 CVE-2026-2441\n\ud83c\udfaf Google Chrome Blink \u2013 Use-After-Free \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/huseyinstif/CVE-2026-2441-PoC\n\n\ud83e\udde0 Overview\nA use-after-free vulnerability in Chrome\u2019s Blink engine enables arbitrary code execution inside the renderer via crafted HTML.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Browser exploitation vector\n\u2022 Potential sandbox escape chaining\n\n\u2796\u2796\u2796\u2796\n\n3\ufe0f\u20e3 CVE-2026-25526\n\ud83c\udfaf Jinjava Template Engine \u2013 SSTI \u2192 RCE\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/av4nth1ka/jinjava-cve-2026-25526-poc\n\n\ud83e\udde0 Overview\nA Server-Side Template Injection vulnerability allowing attackers to execute arbitrary code via crafted template payloads.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 Backend compromise\n\u2022 Application takeover\n\n\u2796\u2796\u2796\u2796\n\n4\ufe0f\u20e3 CVE-2026-26030\n\ud83c\udfaf Microsoft Semantic Kernel \u2013 RCE via Vector Store\n\n\ud83d\udd17 PoC Repository\n\u27a1\ufe0f https://github.com/mbanyamer/CVE-2026-26030-Microsoft-Semantic-Kernel-1.39.4-RCE\n\n\ud83e\udde0 Overview\nA vulnerability in Microsoft Semantic Kernel allows code execution via unsafe vector store handling. Public PoC confirms exploitability.\n\n\u2699\ufe0f Impact\n\u2022 Remote code execution\n\u2022 AI / LLM pipeline compromise\n\u2022 Data processing abuse\n\n\u2796\u2796\u2796\u2796\n\n5\ufe0f\u20e3 CVE-2026-34040\n\ud83c\udfaf Docker Engine \u2013 AuthZ Bypass \u2192 Privileged Container (RCE Chain)\n\n\ud83d\udd17 PoC / Exploit Context\n\u27a1\ufe0f https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2\n\n\ud83e\udde0 Overview\nA critical authorization bypass in Docker Engine allows attackers to bypass security plugins by sending oversized HTTP requests. The request body is truncated before validation, enabling malicious container creation with elevated privileges.\n\n\u2699\ufe0f Impact\n\u2022 Authorization bypass\n\u2022 Privileged container creation (root access)\n\u2022 Full host compromise via container escape\n\u2022 CI/CD & cloud infrastructure risk\n\n\u2796\u2796\u2796\u2796\n\n\ud83d\udcda Research Value\n\u2022 Firmware exploitation techniques\n\u2022 Browser memory corruption exploitation\n\u2022 SSTI \u2192 backend RCE chains\n\u2022 AI/LLM framework attack surface\n\u2022 Modern web framework bypass techniques\n\n\u26a0\ufe0f Intelligence Note\nCurrent GitHub trend:\n\u2022 Strict PoC validation required (fake links increasing)\n\u2022 Browser & AI-related vulnerabilities rising\n\u2022 RCE chains often start from logic bypass\n\u2022 Real exploit repos are limited but high quality\n\n\ud83e\udde0 Cyber Security Exploit Research Community\nMalware Analysis | Reverse Engineering | CVE Research | Threat Intelligence\n\n\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\u2796\n\n\ud83d\udd10 Cyber Security Exploit Community\nTelegram Group\nhttps://t.me/Cyber_Security_Exploit\n\nTelegram Channel\nhttps://t.me/CyberSecurityExploit\n\nResearch \u2022 Ethical Hacking \u2022 Red Team", "creation_timestamp": "2026-08-27T20:00:04.645225Z"}]}