Zero-Day Agent
Know if a zero-day touches you before your scanner can say
Zero-day response starts with knowing which of your assets are affected. The Onit Zero-Day Agent picks up a zero-day as it breaks, finds the affected product in your inventory, and gives every asset a verdict with the evidence.
Book a demoWhy it matters
No plugin yet. Not an issue.
Exploiting a vulnerability is now the number one way attackers get in: 31% of breaches, ahead of stolen credentials for the first time.
A scanner needs a plugin.
The Zero-Day Agent needs a signal.
It picks up the first public signal, including the vendorโs advisory, finds the product in your inventory and checks every version. When a scanner catches up, its finding joins the same exposure.
How it works
From the first signal to a verdict on every asset
Watches for the first signal
From the first public signal through the vendorโs advisory, before a scanner has a check for it.
Reads every signal into one record
Product, affected versions, fix and CVE. Structured data first, a model only for the gaps.
Matches it to your assets
Product and version from data that already exists in your tools, asset by asset.
Gives every asset a verdict
Affected, Likely affected, Not affected or Possibly running, each with its evidence.
Keeps watching
New information or a revised advisory re-matches every asset. When a scanner reports the CVE, its finding joins the same exposure.
When it matters
Quiet until itโs yours
When a zero-day affects your environment, Onit tells you once, clearly, and keeps a live status at the top of your dashboard.
ACTIVE ZERO-DAY
Published by Onit 10h 19m ago
PHP: remote code execution through memory corruption
7 assets running PHP on an affected version
7
AFFECTED
3
LIKELY AFFECTED
4
INTERNET-FACING
- Flagged by Onit
- CVE-2026-109618
- Scanner reports it
No scanner reports it on your assets yet. Onit is tracking it from the first public signal.
WHERE TO FOLLOW IT
- Zero-day page ยท affected assets, what to do now, and every applied advisory update
- Top of your dashboard ยท live status for as long as Onit tracks it
- Exposures ยท each Affected or Likely affected asset gets its own exposure
From the news, October 2026
PHP2Shell was attacked four days before a patch existed.
Four days with no patch
Verdicts
Every answer, with its evidence
Each asset gets one of five verdicts, with the product, version and source behind it.
Affected
The product runs here, on a version inside the affected range
Patch or mitigate now
Likely affected
The product runs here, but no source reports the version
Confirm the version, then treat as affected
Not affected
The version is outside the range or already fixed
Closed, with the version as proof
Possibly running
Only a closed finding mentions the product on this asset
Promote it or dismiss it
Could not trace
No assets found running the product
Nothing to act on. Onit keeps checking.
24 assets. 4 decisions.
A zero-day lands on every asset that runs the product. The agent sorts them by verdict, and each group becomes one decision.
Questions CISOs ask
Straight answers. Anything else, ask us in the demo.
Is this the same as a scanner?
No. A scanner needs a detection for the CVE. The agent starts from the first public signal and your inventory, so it can answer before a plugin exists.
How does it know which assets run the product?
From the product and version data your connectors already send to Onit. Where a source gives the product but no version, the verdict is Likely affected.
What if the agent can't tell?
When a source names the product but not the version, the verdict is Likely affected, not Affected. Every verdict shows the evidence behind it, so your team can see what is confirmed and what is not.
How often does it check?
It watches for new zero-days continuously and re-matches your assets on every data pipeline run.
Can a person review what it publishes?
Yes. Onitโs team can review, edit, retract or retire any zero-day record, and every verdict shows its evidence.
Who decides what happens next?
Your team does. The agent gives every asset a verdict with its evidence, and your team chooses the response. Onit's team can review, edit, retract or retire any zero-day record.
What happens when a scanner catches up?
Its finding is added to the same exposure as another source, and Onit stops tracking it for your account. Anything still unconfirmed after 90 days closes as not confirmed.
Where does it get its signals?
Public sources and vendor advisories, curated by Onit. We donโt publish the list.
What is zero-day response?
Zero-day response is the work of finding out, in the hours after a new vulnerability breaks, which of your assets are affected and what to do first. The Onit Zero-Day Agent does the first part: it picks up the first public signal, matches it to your inventory, and gives every asset a verdict with the evidence.
The next zero-day wonโt wait for a scanner plugin. Your answer shouldnโt either.
See the full product in a demo.
Book a demo