← All security briefings

Security briefing feed format

Each briefing is one checked-in editorial record. The pages, the RSS 2.0 feed and the JSON Feed 1.1 feed are generated from the same record, so all formats carry the same facts.

Feeds

Stable identifiers

  • Every item ID has the form urn:viweb:security:<record-id>:<locale>. It never changes, even if the item is corrected, withdrawn or its URL moves.
  • RSS uses this ID as a guid with isPermaLink="false". The localized detail URL is the item link.

Dates and updates

  • Publication date (RSS pubDate, JSON date_published) is the original publication time and is never rewritten.
  • Substantive modification date (RSS atom:updated, JSON date_modified) advances only for changed scope, fixes, exploitation evidence, guidance, corrections or withdrawal. Items are ordered by this date, then publication date, then record ID.
  • Verification date (_viweb.verifiedAt) records the last full recheck of the critical sources. A verification-only update changes this date and the feed bytes, but not the item ID, the modification date or the order. It is not a new alert.
  • Channel dates come from record data, never from the site build time. Source publication, update and retrieval dates are kept for every source.
  • Not every feed reader notifies on edited items. Check the change history on the briefing page.

States and priority

  • attention: active guidance that is re-verified frequently; flagged as overdue for review more than 72 hours after the last full verification.
  • reference: stable background guidance, targeted for review every 30 days; flagged as overdue after 30 days. It does not mean affected systems are fixed.
  • withdrawn: earlier guidance must not be used. The item keeps its ID and history, shows the reason and holding text, and omits the previous actions, version ranges and exploitation claims. Earlier history entries keep their dates and types, but their text is replaced by a notice that it was withheld; only the final withdrawal entry text is shown. Withdrawn items stay in the feeds.

JSON _viweb extension (schemaVersion 1)

recordId, slug
Immutable record identity and URL slug.
state, priority
published or withdrawn; attention or reference.
identifiers
CVE, GHSA or stable incident keys covered by this briefing.
products
name, slug, affected and fixed ranges as written by the source, plus prerequisites: stable machine condition codes for integrations. Readers see the conditions in guidance.applicability and the item text. Withdrawn items list name and slug only.
exploitation
status (reported, not-established, unknown) and the sourceIds that support it; null when withdrawn.
sources
id, https url, publisher, publishedAt, updatedAt (null when not stated) and retrievedAt.
publishedAt, modifiedAt, verifiedAt
RFC 3339 timestamps with the meanings above.
guidance
impact, applicability, actions (ordered array), unknowns (array), exploitationSummary and statusReason, taken unchanged from the reviewed text of this language. null when withdrawn.
withdrawal
at (date of the final withdrawal entry), reason and holding text; null unless withdrawn.
history
Dated publication, update, correction and withdrawal entries in this feed language. withheld is true when a withdrawn item replaces the earlier entry text with a withheld notice.
relatedBlogUrls
Longer ViWeb articles about the same incident, in this language.
alternate
ID and URL of the same record in the other language.

Use of this data

These are editorial records for website owners and providers. They are not sufficient input for unattended patch decisions and make no claim of complete coverage. Always confirm against the original advisories before acting. Item text is plain text; treat it as text, not HTML.

Curated website and hosting security guidance drawn from public advisories and vendor records within ViWeb's service scope. Entries are general guidance, not a diagnosis of any particular site, and they do not provide complete or real-time coverage. ViWeb researches daily at 10:00 Vietnam time. Entries are published when a useful, verified change exists, so daily research does not mean daily publication. Each entry shows the absolute date it was last verified. Check the original advisories before acting.

Assistant access (MCP)

https://viweb.net/security/mcp

Connect using Streamable HTTP. No account or API key is required. The two read-only tools are search_security_briefings and get_security_briefing, with English (en) and Vietnamese (vi) results.

Tested: MCP 2026-07-28 JSON and 2025-11-25 finite SSE, Claude Code 2.1.316 and MCP Inspector 2.14.0. Other clients are not yet verified. Respect 429/Retry-After responses. Withdrawn records withhold earlier unsafe guidance. These are curated editorial records, not a site assessment or complete vulnerability database; check the original sources before acting.

Connect from Claude Code:

claude mcp add --transport http viweb-security https://viweb.net/security/mcp