CSP-1See your code the way an AI attacker does

Your code has vulnerabilities AI can exploit today.

The good news is CodeSecPilot can find them today. And it is critical that you do that right now. Because AI moved the cost of attack to near zero. Ten years ago, it took an ITSEC expert to find vulnerabilities in your code. Today, all it takes is someone with access to AI to find all the vulnerabilties in your code and ruin your organisation.

start testing

§1How it worksPlanned workflow · illustrative

Run thousands of agents to review your codebase

We run thousands of agents within multiple models and multiple methodologies to ensure we find all vulnerabilities in your code.

MCMaya Chen

First pass: 2,000 agents assess the codebase

4 models · in parallel

Agents2,000all finished

Files1,284indexed · 0 executed

Candidate findings38to re-assess

billing-api @ 8f3c2a1

FileAgents reading

2api/routes/invoices.py
api/routes/exports.py
1api/routes/reports.py
1api/auth/session.py
2api/auth/reset.py
2api/webhooks/payments.py
api/jobs/reminders.py
api/models/invoice.py
1api/cache/keys.py
1api/routes/health.py
api/templates/email.py
1api/payments/refunds.py
1tests/fixtures/keys.py
api/db/session.py

Agents · model

Nothing found
Candidate found

Claude Opus 4.6
Claude Sonnet 4.6
gpt-oss-120b · open-source
gpt-oss-20b · open-source

§3The trapFig. 2 · Illustrative

Found ≠ exploitable

Find vulnerabilities that are actually exploitable

Most organisations get paralyzed after seeing a list of security vulnerabilities. But the reality is that not all vulnerabilities can be exploited by attackers. Companies that are on tight schedules with over-extended roadmaps can rely on CodeSecPilot to help them navigate what really needs to be patched : exploitable attacks with real potential of dammages. Not theoretical vulnerabilities, real problems that can lead to real disasters.

First pass: scanagents read every file

1,906files read · 2,317vulnerabilities found

CriticalPossible SQL injectionreports/export.py:203
HighCross-site scriptingweb/templates/search.html:88
HighOutdated dependency · body-parserpackage-lock.json
MediumWeak hash algorithmlib/crypto/legacy.py:14
HighHard-coded credentialtests/fixtures/env.py:5
MediumAuthorization bypassapi/routes/invoices.py:41
LowInefficient regexutils/validate.ts:31

Second pass: exploitabilitya new agent re-assesses each one

2,317vulnerabilities → 2,302not exploitable · 15real attack path

SQL injection in report sortnew agent · re-assessingNot exploitablesort value checked against a fixed list
Any signed-in customer can open another company's invoicesnew agent · re-assessingExploitableEasy
Hard-coded key in test fixturenew agent · re-assessingNot exploitabletest code only, never deployed
The export page runs database commands an attacker writesnew agent · re-assessingExploitableModerate
Anyone can download another customer's files by editing a file namenew agent · re-assessingExploitableEasy
Open redirect after sign-innew agent · re-assessingNot exploitableonly fixed relative paths allowed
+ 12 more with a real attack pathnew agent · re-assessingExploitable

2,302 not exploitable · kept in History

Fig. 2 · From 2,317 vulnerabilities to 15 with a real attack pathIllustrative · fictional findings

CodeSecPilot is designed to trace how an attacker would reach your data and explain it in words your developer and your CEO both understand, so the right person fixes the right thing first.

§4Need-to-knowPlanned team controls · Fig. 3

Need-to-know only

Keep your vulnerability list confidential.

CodeSecPilot handles the vulnerability list access on a need-to-know basis only: no single developer holds the entire list with all details.

CodeSecPilot assigns each vulnerability to the right developer and developers see only what they really need. Admins and managers see summaries, but not the technical details.

CSP-1 · Fig. 3

TBAdmin · Tom

Any customer can download other companies' invoices→ Maya
An old reset link lets anyone take over an account→ Sam
Fake payment confirmations let orders ship unpaid→ Léa
Customer bank details exposed through a public link→ Maya
Unlimited password guessing on the sign-in page→ Sam
Discount codes can be replayed until an order is free→ Maya

Nothing left here · every vulnerability is with its owner

Routing agent6 sent to their owners

NBNoahsearch
1. nothing assigned
MCMayabilling
1. CSP-142
2. locked
3. locked
IRInèsmobile
1. nothing assigned
SOSamidentity
1. CSP-143
2. locked
KTKaidata
1. nothing assigned
LMLéapayments
1. CSP-147

First vulnerability · readable by its ownerLocked · opens after the current patch is verified

03 / 03Admins see the risk, not the exploit.A routing agent sends each one to the developer who owns the code.Each developer reads only their first vulnerability.

Fig. 3 · The need-to-know workflowIllustrative · fictional people and findings

§5Patch verificationPlanned fix verification · Fig. 4

Make sure vulnerabilities are really patched

CodeSecPilot verifys the original exploit path on a regular basis so you're sure the vulnerability is really patched. Nothing is worse than thinking a vuln is patched, when in reality it's still present in your systems

SOSam Okafor

HighCSP-142billing-apiVerified fixed

Any signed-in customer can open another company's invoices

Commitb71e09dScope invoice lookup to tenant+4−1maya.chen

Verified

CLIcodesecpilot verify CSP-142 --ref b71e09d

MCPverify_finding { "finding": "CSP-142", "ref": "b71e09d" }

Exploit path re-checked at b71e09doriginal exploit path

Invoice lookup now requires the signed-in companyapi/routes/invoices.py:43–46

Every other path to db.invoices.get checked: 2 found, both scopedapi/routes/exports.py:88 · api/jobs/reminders.py:31

Independent second model agrees

Verified fixed at b71e09d3/3 checks passed · the exploit path is gone

Before8f3c2a1 · L43

43 invoice = db.invoices.get(id=invoice_id)

Afterb71e09d · L43–46

43 invoice = db.invoices.get(

44 id=invoice_id,

45 tenant_id=user.tenant_id,

46 )

HighCSP-143auth-serviceReopened

A password reset link keeps working after it has been used

Commitc42d9e0Mark reset token as used+2−1sam.okafor

Checked

CLIcodesecpilot verify CSP-143 --ref c42d9e0

MCPverify_finding { "finding": "CSP-143", "ref": "c42d9e0" }

Exploit path re-checked at c42d9e0original exploit path

Token is now marked as usedsrc/auth/reset.ts:21

The check and the update are two separate steps: two requests sent at the same moment can both succeedsrc/auth/reset.ts:19–21

Still openReopened to Sam Okafor with the new evidence and the complete patch

src/auth/reset.tsc42d9e0 · L19–22

19 const record = await db.resetTokens.findOne({ token });

20 if (!record || record.usedAt || record.expiresAt < new Date()) throw new InvalidToken();

21 await db.resetTokens.update({ token }, { usedAt: new Date() });

22 await users.setPassword(record.userId, newPassword);

Two requests that both read line 19 before either reaches line 21 both pass line 20. The complete patch claims the token in one atomic findOneAndUpdate, then revokes every session.

RuleCloses only when the exploit path is gone. A scan that stops reporting it does not close it.

§6Security metricsPlanned reporting · Fig. 5

How long do your vulnerabilities stay open?

Every vulnerability carries two dates: the scan that found it and the verification that closed it. CodeSecPilot turns them into the figures your board asks for: how many are open, how fast your team fixes them, which repositories carry the risk, and whether the backlog is shrinking.

Only exploitable vulnerabilities count, and one counts as fixed only once its patch is verified.

Counted: Exploitable vulnerabilities only
Fixed: When the patch is verified
Time to fix: From the scan that found it to the verified patch
Scope: Each repository, or all of them

github.com/northstarAll repositoriesLast 6 months

Open now: 42 high · 2 medium
Median time to fix: 6daysHigh 3 days · Medium 11 days
Oldest open: 23daysCSP-143 · auth-service
Fixed: 27of 31found in 6 months

Found and fixed, by month

Found and fixed, by month
	Found	Fixed	Still open
May	9	2	7
Jun	6	5	8
Jul	7	8	7
Aug	4	5	6
Sep	3	4	5
Oct	2	3	4

By repository

Repository	Open	Fixed	Median time to fix	Oldest open
billing-api	10 high · 1 medium	9	4 days	6 days
auth-service	21 high · 1 medium	7	8 days	23 days
payments-gateway	11 high · 0 medium	6	5 days	12 days
web-app	00 high · 0 medium	4	7 days	—
data-pipeline	00 high · 0 medium	1	13 days	—
All repositories	42 high · 2 medium	27	6 days	23 days

Fig. 5 · Security metricsIllustrative · fictional repositories

§10 · Start

The vulnerability is already there. Find it before someone else does.

CodeSecPilot is in private preview. Explore the illustrative review, exploit paths and proposed fixes while hosted scans are being qualified.

start testing