Skip to content

Security Watch 1.2.0

Latest

Choose a tag to compare

@VODuda VODuda released this 19 Nov 17:00
a7ef557

News that no advisory has scored yet gets a level from what the articles say, and findings can show EPSS. Existing configurations and inventories work unchanged. To be published under the default latest tag; the GitHub Action is used as uses: ShieldaAI/security-watch@v1.2.0.

Added

  • News signals. For a news finding with no advisory severity (a zero-day without a CVE, a CVE that is reserved but not published, a vendor bulletin), the articles are read, without a model, for a CVSS score, a vendor's word rating, a report of exploitation, a denial of exploitation and public exploit code. A score or rating raises the finding's priority to at least its level; a report of exploitation raises it to critical, so with urgent_unknown (the default) the finding is sent at once as possibly critical. A statement counts only when it is tied to the finding's subject (its CVE or GHSA identifier, or the product or package it matched); negated and hedged statements and "zero-day" alone are not reports. Signals never lower, dismiss or mark a finding as known exploited, and stop being read once an advisory with a severity joins the finding. Alerts and digests have a News signals: line with the score, rating and subject only; explain shows the sentences they were read from. See news signals.
  • policy.news_signals (default true) turns news signals off.
  • EPSS, optional. sources.epss: true looks up FIRST's EPSS for the CVEs of each current finding (including the CVE aliases of a GHSA-keyed library finding) and shows the highest, with its CVE, in alerts, digests, explain, findings and the scan report (Assessment.epss, exported type EpssScore). Only CVE identifiers are sent to api.first.org, in batches of 50, at most ten requests a scan, each score refreshed once a day. It is shown only: it changes no priority or decision, and a new daily score creates no finding revision, reopens no review and asks no model for a new analysis. A failed lookup is a notice, and findings keep the last score. See EPSS.
  • Assessment.news_signals and the exported types NewsSignals and NewsStatement.
  • The configuration guide lists feeds that carry full articles with scores or exploitation reports (Rapid7, Tenable, The Register, Security Affairs, the Zero Day Initiative) and those that carry only headlines.

Changed

  • Louder for unscored news. A news finding that an article reports as exploited, or that an article scores at 9.0 or above, now alerts at once where 1.1 put it in the digest. Measured on one week of real articles against a 20-product inventory: five findings were raised and one more immediate alert was sent (an actively exploited ScreenConnect plugin). The first scan after the upgrade reassesses news findings still in the news window, so a raised one is sent once.

Not verified

  • Measured on 256 articles from one week of November 2026, labelled by the developer, not by an independent reviewer. The human-labelled pilot and a real Slack and email delivery remain open, as in 1.0.