For technical leads, product owners and teams changing sensitive functionality, inheriting a codebase or investigating a known finding.
When you need root-cause analysis and a practical fix.
What we examine
- Define the modules, changes, dependencies and relevant data flows.
- Review trust boundaries, permissions and handling of untrusted input.
- Investigate findings in context and discuss fixes that fit the architecture.
How I test
Manual review that traces untrusted input to the affected code, mapped to CWE root causes and OWASP ASVS requirements where they apply.
How an engagement runs
Send a short brief
The product, what changed, what you need to know and by when. A paragraph is enough, and I reply within three days.
Get a written proposal
Scope, method, exclusions, deliverables, price and dates. Confidentiality, NDA and retesting terms are agreed in the same proposal.
Follow the work as it develops
For assessments, you see evidence and priorities as they emerge. For engineering, you review the agreed milestones.
Report and walkthrough
You receive the report or the delivered work and a walkthrough with your team. Any further fixes or verification are agreed with you.
I find the cause, then write the fix.
I wrote the patches behind two Linux kernel CVEs and seven more fixes now in mainline. On your product, each finding comes with the code path, the conditions that trigger it and a fix your team can review.
See the 9 merged kernel patchesQuestions before we begin
Which languages and stacks do you review?
I work with application code including C, C++ and Java, alongside a development background in PHP/Laravel, Vue, Node.js and MySQL. Share your stack and review goals so we can confirm the right scope.
Do you need the entire codebase?
Access depends on the question. A focused review may still need surrounding code, build information or tests to understand permissions, dependencies and data flow.
Can the review focus on a proposed fix?
Yes. We can examine whether an agreed change addresses the original cause and whether it introduces related issues. Implementation work is agreed separately where needed.
Can we begin with one component?
Yes. A bounded review of a critical feature, module or change can be a useful first engagement. The report states those boundaries explicitly.
How quickly will you reply?
Within three days at most. You get questions about your product or an outline of the proposal.
What does it cost?
Published prices are starting points. The final price depends on scope and technical complexity and is fixed in the written proposal before work starts.
How long does it take, and when can you start?
Duration and start date depend on the scope, the technical complexity and my current workload. The proposal states the dates.
Can we work under an NDA?
Yes. Confidentiality terms, including an NDA if you need one, are agreed as part of the proposal before you share code, credentials or findings.
Is a retest included?
Retesting is agreed for each engagement in the proposal: which findings, which version and the time window.
Do you work with agencies?
Yes. Agencies can bring me in for a client’s project. Delivery terms, including white-label reports, are agreed case by case in the proposal.
Related reading
- PHP2Shell: CVE-2026-109618 and the Runtime Boundary
- LMCache CVE-2026-105192: execution before rejection
- CVE-2026-21589: Atlassian’s file read that hides behind ::