
Order book
Recent trades
LiveThis market will resolve to “Yes” if a critical vulnerability in PHP is first publicly disclosed between market creation and December 31, 2026, 11:59 PM ET, and meets all requirements below by that deadline. Otherwise, this market will resolve to “No”. Public disclosure means publicly available information sufficient to identify the specific vulnerability, whether through an official advisory, researcher publication, leak, or public code commit. A general warning about an unspecified vulnerability will not alone qualify. A vulnerability publicly disclosed before market creation will not qualify merely because it receives a CVE identifier or qualifying score during the market period. A qualifying vulnerability must affect PHP itself (the PHP interpreter and the extensions bundled in the official php-src source code), must be assigned a publicly available CVE identifier, and must receive a publicly published CVSS base score of 9.0 or higher (under any CVSS version) from either the PHP project or the US National Vulnerability Database (NVD). Vulnerabilities affecting only unsupported PHP versions or optional bundled extensions will qualify if they otherwise meet these requirements. Extensions distributed separately from php-src (for example, through PECL) will not qualify. A qualifying score from either source is sufficient, regardless of a lower score from the other source or under another CVSS version. Only a score published by the NVD itself (attributed to NIST) or by the PHP project will count; scores displayed by NVD but attributed to any other organization will not qualify. Once all requirements have been met during the market period, subsequent score revisions will not affect resolution. CVE-2026-109618 and CVE-2026-109619 (“PHP2Shell”) will not qualify. Vulnerabilities in third-party software written in or running on PHP (for example, WordPress, Laravel, Drupal, plugins, or other frameworks and libraries) will not qualify. The primary resolution source for this market will be official information from the PHP project (including php.net and the php-src GitHub security advisories) and the NVD (nvd.nist.gov); however, a consensus of credible reporting may also be used.
As of November 17, 2026, TwapTrade traders put the chance of “Another critical PHP security flaw in 2026” at 24%, down 8 points in the last 24 hours. $35K has been traded on it. It is scheduled to close on January 1, 2027. Over the past week, the chance has ranged from 17% to 55%; a week ago it was 31%, and it's 24% now.
Prices are traders' live estimates, not certainties. New to this? How to read the odds · More Tech odds
As of November 17, 2026, the market puts it at 24%, down 8 points in the last 24 hours. A Yes share costs about 24¢ and pays $1 if it happens. Prices update live as people trade.
Over the past week, the chance has ranged from 17% to 55%; a week ago it was 31%, and it's 24% now. Prices move as traders react to news, so the chart above shows the full history.
This market will resolve to “Yes” if a critical vulnerability in PHP is first publicly disclosed between market creation and December 31, 2026, 11:59 PM ET, and meets all requirements below by that deadline. Otherwise, this market will resolve to “No”. The full rules are on this page.
It's scheduled to close on January 1, 2027. Until then you can buy or sell shares at the current price.
Create an account with your email, confirm it with a 6-digit code, and deposit crypto from any of 12 networks. Then buy Yes or No at the live price. Trading isn't offered in some countries (the site checks your region), but anyone can follow the odds.
Paste this into any web page or blog post. The card shows the live odds and refreshes itself.
<iframe src="https://www.twaptrade.com/embed/another-critical-php-security-flaw-in-2026" title="Another critical PHP security flaw in 2026? - live odds" width="100%" height="210" style="border:0;max-width:520px;border-radius:12px" loading="lazy"></iframe>
<p style="font:12px sans-serif;margin:4px 0 0">Live odds: <a href="https://www.twaptrade.com/event/another-critical-php-security-flaw-in-2026">Another critical PHP security flaw in 2026?</a> on TwapTrade</p>