Skip to content
patch-gap verification

Patched
≠ fixed.

An advisory tells you a bug was fixed. It doesn't tell you whether a sibling path survived the patch — or whether your stack and config can reach it. The 0day hunter answers with a reproducer, or with the exact reason it doesn't apply.

PHP firstExpanding to other languages, frameworks and software
hunter · advisory → verdictillustrative
advisory ADV-SAMPLE-001 · use-after-free fixed
- if (refcount == 1) free(obj);
+ if (refcount == 1 && !reentrant) free(obj);
? sibling path destructor re-entry
✓ sanitizer heap-use-after-free
✓ reproducer id → uid=33
✗ patched build negative
✗ gadget removed negative
tier → CONFIG-GATED
Illustrative record · loopback lab
the problem

Findings are cheap.
Proof isn't.

AI can spit out vulnerability hypotheses all day. Somebody still has to decide which ones are real on your versions, your config and your apps. The hunter does that work — and won't call anything a finding until a command reproduces it.

the method

Advisory in.
Verdict out.

  1. 01

    Patch diff

    Start from the fix: what changed, and which nearby paths it left alone.

  2. 02

    Hypothesis

    Trace a candidate path through the source to the code your apps actually load.

  3. 03

    Sanitizer proof

    Show the memory or logic fault under instrumentation.

  4. 04

    Reproducer

    Reach a fixed, benign command in an isolated lab. Nothing else counts.

  5. 05

    Controls

    Run it against the patched build and with the gadget removed. Both must fail.

  6. 06

    Tier

    Stamp the result with exactly one precondition tier.

precondition tiers

Every result names
its gates.

Exactly one tier per result: STOCK, CONFIG-GATED or LAB-ONLY. Flip what the reproducer needs and watch the tier move.

What does the reproducer need?

A result moves up a tier only when a gate is removed — never by rewording it.

Our published PHP results: none are STOCK. We say so.

verdict · tier assignmentillustrative
Tier · CONFIG-GATED

Reachable when the named gates hold. Check those gates against your stack.

gates! Needs one named non-default setting, stated in one line, with its own control.! Needs a specific application behavior or delivery shape, stated in one line, with its own control.controls · always run✗ patched build → negative✗ gadget removed → negative
Illustrative tier logic · not a real result
what you get

What lands
on your desk.

Verified reachability

For the advisories that matter to your stack and configuration.

Reproducer evidence

Controls for each result, with its tier and stated limits.

Negative results

So you know what you can safely deprioritize.

Detection packs

For the tools you already run: Sigma, Suricata, ModSecurity.

r&d · php after the patch

We started
with PHP.

On patched PHP 8.4.27 and 8.5.12, a destructor-reentry path still reached freed memory in our local labs. We then followed it into Drupal, Joomla, Roundcube and WordPress and recorded exactly which conditions decide each one. None of it is a default-configuration exposure, and we say so. Our contribution is measurement: patched builds, a control matrix and detection, credited against the prior work we built on.

responsible by construction

Lab-only.
Benign by design.

  • Loopback labs only. No remote targets, no persistence, no lateral movement.
  • A fixed allowlist of benign commands, with scope enforced in code and tests.
  • Prior art credited and negative results published right next to the wins.
built for

Teams that need to know
what's real.

Hosting and platform providers, AppSec teams with large third-party surfaces, software vendors checking that their fixes are complete, and vulnerability-management teams that need verified exploitability, not just scores.

open and enterprise

The method is public.
The feed is the service.

Our PHP research and its repository are already public, and the verification engine is planned as an open-source release. Teams subscribe to the verification feed: verdicts mapped to their inventory, VEX statements, detection packs and a replica of their configuration. Most of the feed is planned; talk to us about early access.

your move

Bring us your stack.

We're working with a small number of teams while we expand beyond PHP.