CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Fortinet FortiGuard PSIRT advisories

fortinet-psirt · A · active

https://www.fortiguard.com/psirt

vulnsvendor-psirtlang: enfetch failures: 0quiet periods: 0last fetch: 2026-10-08

Added 2026-09-29: first-party PSIRT for FortiOS / FortiProxy / FortiWeb / FortiManager and the rest of the Fortinet estate, the most frequently KEV-listed edge vendor; only the FortiGuard research blog existed as a source before. RECIPE: `feed https://filestore.fortinet.com/fortiguard/rss/ir.xml 20` (direct; FG-IR-26-164/165/167 dated 2026-09-08 at probe), then `extract https://www.fortiguard.com/psirt/FG-IR-YY-NNN` for the version table and the 'exploited in the wild' statement. (2026-09-29 operator-directed setup review) | 2026-10-03 S1: `feed https://filestore.fortinet.com/fortiguard/rss/ir.xml` falls to the reader and loses dates; `python3 tools/fetch_source.py url --direct https://filestore.fortinet.com/fortiguard/rss/ir.xml` returns the full XML with pubDate per item (50 items). Read the advisory with `extract https://fortiguard.fortinet.com/psirt/FG-IR-26-NNN`; the page body is the summary, workaround and IoC lists (the added/modified file table that BleepingComputer reproduces did not appear in any 2026-10-03 transport read of FG-IR-26-175). (2026-10-03T0404Z-intel) | 2026-10-06 (S1, main agent verified on FG-IR-26-175): the advisory HTML's 'Download CSAF' href (filestore.fortinet.com/fortiguard/psirt/csaf_<slug>_fg-ir-26-NNN.json, readable with `url --direct`) gives current_release_date and structured remediations; the page's Timeline block names revisions ('2026-10-05: Solution update'), which the RSS pubDate does not.

Cited in 3 entries

Citation cadence

Citation days per ISO week (8 weeks of coverage span, total 2).