Professor Push

0click 0auth RCE in uvdesk, found fully autonomously under project apex with @zauthinc. 73 days since disclosure and no response so heres the PSA and POC 🤷‍♂️

The PHP security team is giving advance notice: Upcoming security release Wed, Oct 21st 2026, 14:00UTC, two critical vulnerabilities, both rated CVSSv4 9.2. PHP users are encouraged to prepare to update. Earlier release if details become public or active exploit evidence.

apologies for the absence on here the past few weeks. i’ve been heads down on development and our client load instead of social media, but i’ll get back to posting more frequent updates. you can join the discord for direct contact with me and the team, link in the replies. as some of you know, we’ve been privately auditing smart contracts for customers and for bounties over the past 3 months. i’ve spent over a month and thousands of dollars getting this software ready to release to the public. our smart contract auditor will work the same way as vector, our pentesting engine. self serve, no human intervention, priced per sloc. when it’s in my own hands i’m confident this is one of the most capable auditing models on the market, but full autonomy is the hardest part. it’s why auditing companies require sales calls and contact before any agreement, and it’s why audits are so slow and expensive. changing this workflow is the whole point of what we’re building at zauth. right now i’m testing vector by feeding it historical hacks. we’re blind testing it against every major smart contract exploit that’s ever happened. if it wouldn’t have caught the vulnerability in an audit, our tooling isn’t good enough yet. we rewind the chain to the block right before each exploit and hand it the source that was deployed at that moment, with no answer key and no hints. it has to locate the bug and construct the drain under the same conditions the original attacker faced. identifying the type of bug is close to solved. the hard part is proving you can actually drain it. that means chaining the contracts together the right way, blind, on a real fork, and doing it reliably on large codebases. that’s where most of my effort is going. we plan to release in two stages. evm first, currently covering ethereum, bsc, base, arbitrum, polygon, robinhood chain and more. solana will follow, since it has a completely different runtime and a different exploit model. reinventing how security gets done is no small task, but if you look at what zauth has delivered over the past 10 months you’ll see why i quit my job and went full time on zauth. i am betting everything on us winning.

We’re currently working with @zauthinc to audit Agent Wormhole’s hosted API and x402 payment flow. Security products should be held to the same standard they ask everyone else to meet. We want the layers protecting agent payments and execution to be tested by people whose job is finding where systems break.

The best hackers on the internet don't work for you, but starting now, one of them does. We built an agent that hunts vulnerabilities like an attacker does. Until now it's only run where a customer asked. Introducing Project Apex. We're unleashing Vector on production systems, and we're going to find serious vulnerabilities. Smart contracts, repositories, packages, you name it. We published a benchmark where our engine outperformed a far larger incumbent, but a paper only proves so much. A benchmark is a controlled room. The field isn't. The gap between "best on paper" and "best in practice" is where security tools fail, and the only way to close it is to show our work publicly. The benchmark is our claim. We've built one of the most powerful pieces of cyber defense on the internet. Apex will be the receipt.