Zero Day Room
Live

Latest Cybersecurity news

More to read

Briefings

Fireworks AI suffered two October breaches where hackers stole billing data and AI-specific information, with a...
Threats

Fireworks AI breach exposes customer data in LLMjacking attack

Fireworks AI suffered two October breaches where hackers stole billing data and AI-specific information, with a third-party cloud attack enabling unauthorized workloads. The incident impacted Notion's systems and exemplifies the rapid financial fraud risk of LLMjacking attacks targeting AI infrastructure.

Zero Day Room desk 10 Nov 2026

Profiles

Atlassian Confluence

Atlassian Confluence

Enterprise wiki and collaboration software · Team workspace for creating, sharing, and...

Data and guides

Also this week

U.S. agencies warn that threat actors are actively targeting industrial refrigeration and cold-chain monitoring systems...
Threats

Industrial refrigeration cyber attacks sweep Europe

U.S. agencies warn that threat actors are actively targeting industrial refrigeration and cold-chain monitoring systems globally, exploiting unpatched controllers to alter temperatures, cause inventory loss, and create fire hazards.

9 Nov 2026

Browse sections

Common questions

What does Zero Day Room cover?

The vulnerability or campaign, and the patch or control that stops it, with an Asian regional focus. Vulnerabilities and Threats hold the offensive side as reported, Defence holds the mitigations, Regulation & compliance covers the legal duties, and Incidents follows breaches as they are disclosed.

Do you publish exploit code?

No. Coverage is defensive: pieces describe what has been disclosed, what is affected and what the vendor or advisory recommends, without proof of concept code or step by step exploitation.

Where do the advisories come from?

From vendor advisories, national cyber agencies, researchers and named publications, credited and linked in each piece. Severity ratings belong to whoever assigned them, and the vendor's own advisory is the version to patch against.

Is an incident reported here confirmed?

Only as far as the source says. Attribution and breach scope change repeatedly in the days after disclosure, and a piece reports who claimed what rather than settling it. Attacker claims are reported as claims.

Why is the source credited instead of a writer?

Nobody is bylined. Pieces are written with automated assistance from the source material, and the advisory or publication behind them is credited in place of an author.

How quickly does the site update?

As the sources publish, which for a widely exploited flaw means several pieces in a day as details change. Anything you are acting on should be checked against the current advisory rather than the summary.