Apex finds real, exploitable vulnerabilities in mission-critical code and hands your team
fix-ready guidance in a workspace built for validating and shipping fixes.
A shared-token-authenticated same-LAN caller can spoof Control UI locality, silently pair an
admin device, and retain admin authority after shared-token rotation.
Proof of concept
Copy
1const config = {
2 gateway: {
3 bind: "lan",
4 auth: { mode: "token", token },
5 controlUi: {
6 enabled: true,
7 allowedOrigins: [`http://localhost:${port}`],
8 },
9 },
10};
Recommendation
Verify the immediate peer before trusting proxy headers; derive scopes from stored
paired device records.
02Fix review
Ship the fix. Apex re-tests it.
Link a pull request and Apex replays the original proof of concept against it. A
successful retest verifies the candidate patch. Merging and deployment are separate steps.
Apex re-tests each linked PR against the original proof of concept.
2 need attention
All · 4Needs attention · 2Active · 1Confirmed · 1
Fix confirmed OPEN-2
Paired chat users can mint a setup code that silently auto-promotes a durable operator device
OpenClaw penetration test · openclaw/openclaw · #287
Fix confirmed in the latest review.
Open PR
Fix in review OPEN-6
First-time node connects expose system.run before node-pair admin approval
OpenClaw penetration test · openclaw/openclaw · #296
Fix review is checking the candidate patch.
Open PR
Not verified OPEN-3
Spoofed Control UI locality silently mints persistent admin device tokens
OpenClaw penetration test · openclaw/openclaw · #291
A patch-verification result is not included in this example.
Open PR
03Scans & schedule
Connect in minutes. Findings in a few hours.
Connect GitHub, pick repositories, and watch the scan progress live. Set a weekly or
daily schedule and every new commit range gets the same treatment.
Penetration test running· scanning openclaw/openclaw13m 57s
ETA ~15m · +3 newView
First scan completeSchedule the next scan to keep this workspace current. Set schedule
Schedule scans
Future scans start automatically on this cadence.
Weekly · Monday at 9:00 AM UTC
Daily · 9:00 AM UTC
Manual only
Next run: Mondays at 9:00 AM UTC.
04Threat model
Hunts guided by your threat model.
Before a scan starts, Apex writes a threat model for the repository: what an attacker can
reach, which impacts matter most, and what to ignore. Edit it, then let the hunters
optimize for it.
OpenClaw threat model
threat_model.md · Generated Apr 24, 2026
Copy
Edit threat model
Expand
THREAT_MODEL
Scope Summary
This repo is an AI agent gateway/control-plane system. The highest-value findings
turn untrusted chat, web, API, or plugin input into
operator-equivalent control over the Gateway, paired nodes,
browser state, secrets, or host execution.
Prioritized Impacts
Unauthorized host exec on gateway or node100%
Sandbox escape to host or node99%
Gateway auth / trusted-proxy / pairing bypass98%
Credential theft with durable replay value97%
05Where you work
Findings land where your team already works.
Summon a PR scan from a GitHub comment, or run the whole loop from your terminal: scan,
watch progress, triage findings, and kick off fix reviews.
GitHub Comment @cantina-apex scan this pr and the review lands on the PR Check passed
Trackers Send findings to Linear or Jira, or export a penetration test report in Markdown Export
Sharing Passphrase-protected, client-safe views of the workspace apex.cantina.security/share/8f3a…
Proof, not promises
Trained on real security assessments, not synthetic data
n01
50,000+
Real-world vulnerabilities analyzed
n02
9,000+
Expert security researchers contributing signal
n03
10+
Criticals and highs found in production code
n04
$25B+
In live funds secured
I was truly impressed by the subtle bugs that Cantina uncovered in an open-source
cryptographic repository that I maintain, which had already gone through thorough reviews.
Their AI-powered tool acts as a valuable safety net to catch bugs that humans and other tools
may have missed.
Arash Afshar · Coinbase Cryptography Team
FAQ
Questions, answered.
What teams usually want to know before connecting their first repository.
Apex uses AI-assisted code understanding to surface practical vulnerabilities, reduce false positives, and provide remediation guidance with context.
Yes. You can connect private repositories through your GitHub integration and control scan scope by repository, branch, pull request, or commit.
Yes. You can target specific branches, PRs, and commits, and include contextual documents to improve scan accuracy for your codebase.
Teams can comment on findings, validate or dismiss issues, and share views externally through passphrase-protected links.
Most teams can run their first scan in minutes after connecting repositories and setting up a workspace.
See your first findings today.
From a single scan to enterprise coverage, Apex shows what matters and helps your team fix it
fast.