Rapid7 Research

https://www.rapid7.com/blog/

Rapid7 vuln and incident research; Metasploit project; weekly Metasploit Wrap-Up. RSS at https://www.rapid7.com/rss.xml. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → feed https://www.rapid7.com/rss.xml 5 (feed carries full HTML body incl. CVE detail; per-post URL drill optional). AVOID: Don't WebFetch the /blog/ landing page, the rss.xml feed already returns full post bodies with CVE IDs and module detail.. | 2026-06-30: a sub-agent hit HTTP 404 on https://www.rapid7.com/blog/feed/, that is the WRONG endpoint. Correct feed is https://www.rapid7.com/rss.xml (already documented above). Source healthy; no demotion. | 2026-07-05 admiralty audit: B, original vendor vuln/incident research + Metasploit wrap-ups. Live and fresh (daily/weekly). Active retained; use rss.xml (not /blog/feed/). | 2026-09-29: rss_url pinned to https://www.rapid7.com/blog/feed/ (fetch_method is rss but the feed lived only in the notes, so it never reached the research slice). (2026-09-29 operator-directed setup review) | 2026-10-05 S1: the pinned /blog/feed/ returns 404; https://www.rapid7.com/rss.xml is the working feed (dated items, direct transport, re-verified by the main agent). | 2026-10-18 (S3): the feed https://www.rapid7.com/rss.xml is malformed (invalid token near line 367) and the reader returns nothing; `extract https://www.rapid7.com/blog/` lists /blog/post/<slug>/ links without dates and `extract` of each post returns the date. | 2026-10-19 intel run S3: feed https://www.rapid7.com/rss.xml is malformed XML and the reader returns no items; `extract https://www.rapid7.com/blog/` returns /blog/post/ hrefs without dates, then `extract <post URL>` gives the date. | 2026-10-20 (2026-10-20T0256Z-intel) S1: both `feed` URLs fail on malformed XML; working recipe is `url --direct https://www.rapid7.com/blog/rss/` then a regex over the <item> blocks (20 dated items) and `extract` of the exact <link> (a truncated slug falls to the reader and returns a 404 shell). It surfaced the NetScaler incident analysis this run. | 2026-10-23 (S3): recipe: rss.xml is not well-formed XML; `extract https://www.rapid7.com/blog/` returns the newest four headlines without dates and the quarterly report page reads with `extract`. | 2026-10-24 (S3): https://www.rapid7.com/rss.xml returned an error through `feed` this run (rc=1, empty body); `extract https://www.rapid7.com/blog/` returned a 535 KB Next.js page without per-post dates in extractable form. Not in this slice; the 2026-10-23 S3 run already covered Rapid7's Q3 report. | 2026-10-25 (S1/S3): `feed https://www.rapid7.com/rss.xml` fails (not well-formed XML / empty body); `extract https://www.rapid7.com/blog/` lists /blog/post/<slug>/ hrefs without dates and per-post `extract` carries the date. | 2026-10-26 (S3): https://www.rapid7.com/rss.xml is not well-formed XML; `extract https://www.rapid7.com/blog/` returns raw HTML with `/blog/post/<slug>/` hrefs and no dates, and `extract` of each post carries the date in its metadata. | 2026-10-27 (S3): the `feed` subcommand errored this run; `url https://www.rapid7.com/blog/` returned the listing with hrefs.