For desktop software, library, SDK and developer-tool vendors working with C, C++ or Java and components that handle untrusted input.
When introducing a parser, protocol, library or important native component.
What we examine
- Define target components, operating environment, build requirements and trust boundaries.
- Examine relevant code, input processing and application behavior.
- Use code review, dynamic testing or targeted fuzzing as agreed for the target.
How I test
Code review, dynamic testing or fuzzing as agreed, with findings mapped to CWE root causes.
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
What kinds of desktop projects are relevant?
Applications, libraries and components with clear security questions, especially around untrusted input. Share the language, operating system and build requirements so we can confirm fit.
Is fuzzing part of the assessment?
It can be included when suitable for the target. We agree the feasibility work, campaign and artifacts separately rather than assuming every application needs the same approach.
What public work supports this offer?
My public work includes CVE-2024-26855 and CVE-2025-37858 in the Linux kernel, with fixes accepted upstream. Those records show specific native-code investigation and remediation work.
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
- The Asterisk Paradox: CVE-2026-123158 and the OpenSSH–musl Authentication Bypass
- PHP2Shell: CVE-2026-109618 and the Runtime Boundary
- Lovable and Supabase security checklist: what to check before launch