Security Advisories

Security advisories are source-reviewed notices about security issues, affected product scope, available actions and subsequent changes. Each advisory shows its scope, what is not yet established, and the date of its latest revision. An advisory is not the same as a service-status incident or a vulnerability submission.

Security professionals reviewing documents in an office
Monitored components
Monitored components
Timestamps shown
Timestamps shown
Support routes
Support routes
Planned maintenance
Planned maintenance
SOURCE CURRENCY

Last verified time appears here only when a verified source timestamp exists.

Times are shown with their timezone. A cached result is never shown as current.

VERIFICATION PENDING

Four things that are easy to confuse

Each record type has its own owner, its own page and its own meaning. Use the link that matches your question.

Security advisory

A source-reviewed notice about a security issue, its scope and actions.

This page

Service status

Current operational health of services. Not a security bulletin.

Availability and status page

Vulnerability report

A report you submit about a suspected issue.

Responsible Disclosure route

Release change

What changed in a product or SDK version.

Changelog

Search, filter and sort published advisories

The list reads only approved public records. Filters appear only for values the source supports.

Product area

Published date

Lifecycle

0 advisories match these filters

No advisories match these filters

This does not mean there are no security issues. Reset your filters, or read the Security contact route if you need help.

Advisory information is temporarily unavailable

If the list cannot be loaded, we will not show a cached result as current. Contact the Security contact route for urgent questions.

State shown when the source is unavailable. Not shown as a live result.

What each card shows, with no placeholder notices

Each card carries an advisory ID, a title, approved tags, the published and updated dates in the visible timezone, and one text action. Cards below are layout guides only.

Professional working at a desk
LAYOUT GUIDE

Advisory ID and title

Opaque stable ID, then the approved title.

Published and updated dates, with timezone
Papers and stationery on a desk
LAYOUT GUIDE

Scope and tags

Affected scope only where verified. Unknown stays labelled unknown.

Never "all products unaffected"
Professional sitting at a desk smiling
LAYOUT GUIDE

Lifecycle

Current, Updated, Superseded or Withdrawn, as the record states.

No "resolved" label without confirmation

Four states of scope, none inferred

An advisory can name a product or version as affected, not affected, not yet evaluated, or unknown. Your deployment may differ from the general statement.

AFFECTED

Named in the record.

NOT AFFECTED

Named explicitly with its version.

UNDER ASSESSMENT

Not yet evaluated.

UNKNOWN

Not established in the record.

Professional discussing technical scope with a colleague

What every advisory page must answer

The template below lists the fields a published advisory fills in. Values shown are placeholders, not an advisory.

TEMPLATE - NO ADVISORY SHOWNADVISORY ID: ASSIGNED ON PUBLICATION

Advisory title

Approved title, reviewed for accuracy.

SUMMARY

Plain-language issue and relevance.

SEVERITY OR PRIORITY

Source-approved, or unspecified.

Not yet established
AFFECTED PRODUCTS AND VERSIONS

Structured per product and version.

Under assessment
PUBLISHED AND UPDATED

Absolute time with timezone.

IMPACT AND EXPLOITATION

Approved factual disclosure only.

Not published
RECOMMENDED ACTION

Approved steps, with ownership.

Not yet approved
MITIGATION STATUS

Known, guidance available, revised or superseded.

RELATED RECORDS

Changelog, status or documentation links, if traceable.

Laptop displaying code on a desk

Revision history

Every substantive change is recorded with its date and reason. Earlier versions stay available, and corrections are labelled.

Professionals collaborating in an office environment

Who approves

Security response owns the facts. Legal, Privacy and Communications review wording before publication.

Actions come only from approved guidance

When an advisory has approved guidance, it appears above the revision history, with its owner. Until then, the panel directs you to the Security contact and to official updates.

Read the scope before acting.
Follow only approved remediation steps.
Contact the Security contact route if your scope is unclear.
Two professionals discussing technical details at a workstation

Organization-specific details need sign in

Account-specific information is available only to entitled, signed-in organization members through an approved secure route. It is never shown on this public page.

Sign in for entitled details

Private details stay private

Customer-specific evidence is never published. Public advisories describe the issue; the entitled annex, where implemented, describes its effect on your organization.

Server-side entitlement checks.
No existence leakage to unauthorized visitors.

Each question has its own page

Availability status team collaboration

Availability status

Current service health.

Security contact discussion

Security contact

Questions about an advisory.

Trust Center review

Trust Center

Approved assurance information.

Changelog planning session

Changelog

Product and SDK changes.

Modern office interior background

Find the advisory that applies to you, or contact the security team.

Security actions come first. Enterprise discussion is available once your immediate question is answered.

Frequently asked questions