Skip to content
snailsploit[$]
external research receipts

References.

Source-verified ledger of independent public acknowledgements, researcher credits, and security-database attribution. Every entry links to an upstream or third-party source — none are self-reported.

20
verified receipts
11
gold-grade
11
first-party
6
intel databases
17
organizations

Classification

This is not a CVE-count report. The strongest evidence is that upstream security organizations themselves publicly identify Kai Aizen / SnailSploit as the reporter or finder.

A+ — Gold First-party vendor/upstream source explicitly credits Kai Aizen / SnailSploit as reporter, finder, or independent discoverer. A — External Independent security-intelligence/database source or corporate propagation that preserves attribution. B+ — Third-party Independent security research or commentary that discusses the finding and its attribution. Excluded Own site, GitHub repos, LinkedIn, self-authored CVE pages, and direct copies of own material are not counted.

First-Party Attribution A+ · 11 receipts

HashiCorp — Consul CVE-2026-19017A+
“CVE-2026-19017 was reported to HashiCorp by Kai Aizen / SnailSploit (‘The Jailbreak Chef’).”
vendor / upstream
First-party HashiCorp security advisory. Gold-standard receipt.
discuss.hashicorp.com →
Kubernetes — ingress-nginx CVE-2026-3288A+
“This vulnerability was reported by Kai Aizen.”
vendor / upstream
Kubernetes Security Response Committee acknowledgement.
groups.google.com →
Symfony / Twig CVE-2026-46627A+
“We would like to thank Kai Aizen (Snailsploit) for reporting the issue.”
vendor / upstream
First-party Symfony security advisory.
symfony.com →
Jenkins — Assembla / Contrast Plugins SECURITY-3692 · SECURITY-3697A+
Jenkins thanks Kai Aizen (SnailSploit) for discovering/reporting four issues.
project security advisory
One first-party advisory credits four separate security issues.
jenkins.io →
Jenkins — Sauce OnDemand Plugin CVE-2026-70445A+
“dyingman1 … and independently, Kai Aizen, SnailSploit”
project security advisory
Especially strong: the project explicitly records an independent discovery.
jenkins.io →
Apache Airflow — Core CVE-2026-30911A+
“Credit: Kai Aizen (finder)”
upstream security mailing list
Apache security disclosure carried through oss-security.
openwall.com →
Apache Airflow — Databricks Provider CVE-2026-32794A+
“Credit: Kai Aizen (reporter)”
upstream security mailing list
Second distinct Apache Airflow attribution.
openwall.com →
Oracle — Product Security CVE-2026-61308A+
Oracle’s August 2026 Critical Security Patch Update lists “Kai Aizen : CVE-2026-61308” in its contributor credits.
vendor cpu
Enterprise-vendor security credit alongside established security research organizations.
oracle.com →
ddev — GitHub Advisory CVE-2026-32885A+
“Credit: Kai Aizen (SnailSploit) — Adversarial AI & Security Research.”
upstream advisory
GitHub Advisory Database entry published from the ddev project.
github.com/advisories →
PraisonAI — GitHub Advisory CVE-2026-55528A+
“Credit: Kai Aizen — SnailSploit (@SnailSploit).”
upstream advisory
Project-owned GitHub Security Advisory.
github.com/MervinPraison →
vLLM — GitHub Advisory CVE-2026-54236A+
“Researcher: Kai Aizen — SnailSploit (@SnailSploit).”
upstream advisory
Upstream advisory explicitly identifies the researcher.
github.com/advisories →

External Attribution A · 8 receipts

IBM — Consul Bulletin CVE-2026-19017A
“This issue was reported to HashiCorp by Kai Aizen / SnailSploit (‘The Jailbreak Chef’).”
corporate propagation
Independent IBM support/security surface reproducing the upstream acknowledgement.
ibm.com →
CloudBees — Jenkins Ecosystem CVE-2026-70445A
CloudBees reproduces the Jenkins credit, including “independently, Kai Aizen, SnailSploit.”
corporate propagation
Corporate security advisory mirroring the upstream Jenkins acknowledgement.
cloudbees.com →
Snyk — ArcadeDB CVE-2026-54076A
Snyk lists the credit as Kai Aizen.
security database
Independent commercial security-intelligence database.
security.snyk.io →
Snyk — vLLM CVE-2026-54236A
Snyk lists “credit SnailSploit | Kai Aizen.”
security database
Independent commercial security-intelligence database.
security.snyk.io →
Wordfence — Researcher Profile Researcher profileA
Wordfence maintains a dedicated Kai Aizen researcher profile containing multiple credited vulnerabilities.
researcher database
Strong external footprint from independent security platform.
wordfence.com →
Positive Technologies — dbugs CVE-2026-3594A
Positive Technologies’ dbugs researcher record identifies Kai Aizen for the vulnerability.
security database
Independent security company/database surface.
dbugs.ptsecurity.com →
Kodem Security — ArcadeDB CVE-2026-54076A
“Reported by Kai Aizen (SnailSploit).”
security intelligence
Independent security-intelligence company explicitly carries the reporter attribution.
kodemsecurity.com →
Miggo Security — vLLM / ArcadeDB CVE-2026-54236 · CVE-2026-54076A
Miggo records Kai Aizen / SnailSploit as researcher or reporter for these findings.
security intelligence
Independent security-intelligence surface; multiple findings found.
miggo.io →

Third-Party Research B+ · 1 receipt

CELVEX Group — ingress-nginx CVE-2026-3288B+
Third-party attack research explicitly notes the Kubernetes advisory’s credit to reporter Kai Aizen.
third-party research
Not a vendor acknowledgement; valuable because an unrelated researcher discusses the finding and attribution.
celvexgroup.com →

Linux Kernel — Upstream Receipts

Security-research receipts show vendors crediting you for finding vulnerabilities. Kernel receipts show upstream maintainers accepting security fixes and carrying authored code through mainline and stable Linux releases. Different credibility axis.

9
kernel receipts
3
CVE-linked
2+
stable/mainline
∞
LKML interactions
SubsystemCVEEvidenceStatus
io_uring/zcrx CVE-2026-43121 Upstream io_uring pull lists Kai Aizen as the author; stable patch is explicitly “From: Kai Aizen.” oss-security identifies the commit, author, and notes it was already in stable. [1] [2] mainline + stable
iommufd — Linux IOMMUFD pull request lists Kai Aizen as contributor; 7.1.4 changelog records commit and author. Greg Kroah-Hartman replied directly to the patch submission. [1] [2] mainline + stable
RDMA/ionic CVE-2026-53371 Jason Gunthorpe replied, fixed the diff, added a Fixes tag, and thanked the author. [1] upstream + maintainer
net/rtnetlink CVE-2026-46132 Linux 7.0.7 and 6.18.30 changelogs record Kai Zen as author of the stack-infoleak fix. [1] stable kernel
net/tipc — Stable/netdev threads show the patch authored by Kai, with detailed UAF analysis, Signed-off-by, and kernel test-robot tracking. [1] patch / review
Bluetooth/hci_conn — Kernel Bluetooth mailing-list trail contains the security fix submission under Kai Aizen. [1] upstream submission
USB gadget/UVC — Linux release discussions include Kai Aizen among kernel contributors for a USB gadget/UVC fix. [1] release evidence

What This Establishes

  1. First-party attribution. Multiple upstream projects and vendors publish the attribution themselves. The evidence is not dependent on SnailSploit’s own CVE pages.
  2. Cross-ecosystem footprint. Verified receipts span cloud/infrastructure (HashiCorp, Kubernetes), developer infrastructure (Jenkins), major OSS projects (Symfony, Apache), enterprise software (Oracle), AI infrastructure (vLLM, PraisonAI), and security-intelligence providers.
  3. Unusually strong receipts. Jenkins explicitly uses the word “independently” when crediting Kai Aizen. Kubernetes names the reporter in a Security Response Committee acknowledgement. HashiCorp says the issue was “reported to HashiCorp by Kai Aizen / SnailSploit.”
  4. Secondary amplification. Snyk, Wordfence, Positive Technologies, Kodem, and Miggo independently expose the researcher identity in their security-intelligence surfaces.

Research pass completed 24 August 2026. Prepared from live web sources. This is not an exhaustive census — search-engine indexing is incomplete, and some vendor portals are difficult to crawl. These are verified receipts found in this research pass.