Ivanti Security Advisories

https://www.ivanti.com/blog/topics/security-advisory

Added 2026-09-29: first-party advisories for Connect Secure / Policy Secure / EPMM / Neurons (edge and MDM lines with repeated exploitation). RECIPE: `feed https://www.ivanti.com/blog/topics/security-advisory/rss 10` (direct; monthly roundups, newest 2026-09-08 at probe), then drill the linked per-product advisory on forums.ivanti.com. Out-of-band advisories may be posted only on the forum; KEV, EUVD and CERT relays cover those. (2026-09-29 operator-directed setup review) | 2026-10-14 intel run: hub.ivanti.com advisory pages (forums.ivanti.com redirects there) are JS-only on url, extract, WebFetch and jina, so the advisory text is unreadable in the container. The RSS reads direct and lists the monthly security-update posts, each readable with extract (https://www.ivanti.com/blog/october-2026-security-update); the affected/fixed table is then read through Rapid7 or Volexity. Rotate into S1 on every second Tuesday. | 2026-10-19 intel run S1: RSS and `extract` of the monthly security-update post work, the post lists no CVEs and the advisory hub stays JS-only on every transport; read the affected/fixed table through Rapid7 or Volexity. | 2026-10-20 (2026-10-20T0256Z-intel) S1: the state fetch-gap id ivanti-advisory-hub is not a record; the real record is this one. Monthly post reads via RSS + `extract` but lists no CVEs; hub.ivanti.com and forums.ivanti.com are unreadable on every transport.