The WordPress Security Team has received more than 3,000 vulnerability reports so far in 2026, which it says is more than in the previous twelve years combined. The figures come from an update by Rudy Faile, published on the project's Making WordPress Secure blog on 29 October 2026.
The post reports on the first two months of the Core Security Initiative. It says the team has built AI tooling that now searches WordPress core for vulnerabilities before anyone reports them.
Background
The team announced the Core Security Initiative on 28 August 2026, saying the project had seen "a substantial increase in the volume of incoming security reports". The initiative has three pillars, which the team calls "ABC": a better release process, breaking the backlog, and crushing vulnerabilities with AI. WordPress receives most of these reports through its bug bounty programme on HackerOne.
From 30 reports a month to hundreds
According to the 29 October update, the HackerOne programme received 20 to 30 reports a month for about a decade. It received 450 in July and 773 in August. The post says the programme page showed 2,306 reports in the past 90 days when it was written.
“A lot of this is real research made faster by AI tools, and it’s making WordPress safer.”
Rudy Faile, WordPress Security Team, 29 October 2026
The post adds that "everything after a report lands (triage, fixing, backporting, testing, shipping) has to move faster too."
Four security releases in 41 days
The update lists four core security releases in 41 days: WordPress 7.1.1 on 17 September, 7.1.2 on 22 September, 7.1.3 on 6 October and 7.1.4 on 28 October. The team says that makes seven core security releases since mid-July, with more than 50 vulnerabilities rated Critical or High closed.
Every fix went to every branch still receiving security updates, back to WordPress 4.7. Releases now ship in two waves, with the most widely used versions first and older branches after.
Backporting a single fix used to mean running scripts by hand across up to 25 branches. The post says 73% of the 109 steps in a security release now have automation. Some steps stay manual on purpose. Only a small group can package a release, which the team says helps protect against supply chain attacks.
AI triage cut the backlog
On 1 September the team updated its disclosure programme to focus on issues with clear security impact. For in-scope assets other than WordPress core and Gutenberg, issues "requiring a role that can only be granted by an administrator", such as Contributor, will generally no longer be eligible unless they show a high-severity escalation. Core and Gutenberg keep the existing rules for now.
The team also built an AI-powered triage system. It reads incoming reports, reproduces them securely, and posts a summary and a recommendation on validity and severity. The post says security researchers still make the final call.
The team says it has closed nearly 3,000 reports this year. The untriaged queue has fallen from 359 to double digits.
Looking for bugs before they are reported
“The agentic tooling we built to triage incoming reports, which reads the code and checks whether a report holds up, is now pointed the other way: hunting for vulnerabilities in core before anyone reports them.”
Rudy Faile, WordPress Security Team, 29 October 2026
The team says it runs this tooling with open weight models and purpose built harnesses, and that anything it finds goes through the same release process. WordPress has also enrolled in Anthropic's OSS Scanner, which the post describes as giving open-source projects free security scans. The team says it has started fixing issues from the first scan results and credits Anthropic in release announcements.
The post asks researchers to read the updated guidelines before reporting: "One clear, high impact report helps more than ten informative or out of scope reports." It asks businesses that run on WordPress to help by "sponsoring people for triage and release work, and contributing to the bounty program."
What this means for site owners
Analysis by Depakar B
Security releases are now arriving every few weeks, and the team's figures suggest that will continue while report volumes stay high. The WordPress 7.1.4 announcement repeated the usual advice: "it is recommended that you update your sites immediately."
WordPress.org says that on sites supporting automatic background updates, "the update process will begin automatically." If auto-updates are switched off, or a host or management tool controls them, check the version number after each release rather than assuming it updated. My report on what WordPress 7.1.4 fixed covers the latest release.
The initiative covers WordPress core. Plugins and themes are patched by their own developers and still need their own update routine. My website maintenance service covers that work if you want to hand it off.
About this report
This report is based on official posts from the WordPress Security Team on make.wordpress.org and release announcements on WordPress.org News. Facts and quotes are taken from the sources credited below, which I re-read on 3 November 2026. Sections marked "Analysis" are my own view. I am an independent WordPress developer and am not affiliated with the organisations named here.
Credits and sources
- Source: Rudy Faile, WordPress Security Team, Making WordPress Secure (make.wordpress.org/security), 29 Oct 2026: The Core Security Initiative: two months in
- Source: Rudy Faile, WordPress Security Team, Making WordPress Secure (make.wordpress.org/security), 28 Aug 2026: The Core Security Initiative
- Source: Ehtisham Siddiqui, WordPress Security Team, Making WordPress Secure (make.wordpress.org/security), 1 Sep 2026: Updates to the WordPress Vulnerability Disclosure Program
- Source: Aaron Jorbin, WordPress.org, WordPress.org News, 28 Oct 2026: WordPress 7.1.4
- Source: WordPress, HackerOne, programme page: WordPress bug bounty programme
- Lead image: Illustration created for this article: AI-generated background, with headline text added by Depakar B.
Corrections
Updated 5 November 2026, 11:40 IST:52 IST: the description now names the WordPress Security Team as the source, the analysis wording on automatic updates now follows the WordPress.org release note, and a background section, quotes and full source credits were added.
Spotted an error? Please contact me. Corrections are noted on this page with the date.