---
title: 'In the News: November 14, 2026 (Extra 3)'
description: 'Project Zero will publish bug details 90 days after reporting, falling to 30 by 2028, citing faster LLM-assisted exploitation.'
canonical_url: 'https://darkfactory.dev/news/2026-11-14-extra-3'
markdown_url: 'https://darkfactory.dev/news/2026-11-14-extra-3.md'
collection: news
date_published: '2026-11-14T23:05:00-05:00'
date_modified: '2026-11-14T23:05:00-05:00'
---

# In the News: November 14, 2026 (Extra 3)


Google's Project Zero now publishes vulnerability details a fixed number of days after it reports them, with no grace period, and that number drops from 90 to 30 by January 2028. It cites LLM-assisted discovery and exploitation as the reason. Also here: a Codex CLI change that affects headless runs in untrusted checkouts, opencode moving subagents to the background by default, and a scan of exposed data in Lovable-built apps.

## 1. Project Zero moves to a fixed disclosure deadline and cites LLMs

**[Policy and Disclosure: 2026 Edition](https://projectzero.google/2026/11/disclosure-policy.html)** · Natalie Silvanovich, Google Project Zero · Project Zero blog, November 13, 2026

Since 2021 Project Zero has given vendors 90 days to fix a reported bug plus 30 days of soak time for the patch to roll out. The new policy drops both. Under what it calls "Full X", details are disclosed X days after the report, whether or not a fix has shipped. The policy is Full 90 from November 13, Full 60 from February 2, 2027, and Full 30 from January 3, 2028. Grace periods and the variant policy are gone. The only exceptions are bugs exploited in the wild, bugs already made public by others, and vendor requests for disclosure.

The post gives LLMs as the cause. It says attackers now find and exploit bugs faster, that several parties are more likely to find the same bug, and that a patch gives away its bug almost at once, so that "zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior." Project Zero also says LLMs have raised its own reporting volume to several bugs a week in targets where it once found a few a year. These are the team's own observations; the post gives no wider dataset.

**Why it matters:** Project Zero is saying that soak time no longer protects users, and that the gap between a report and public details will be 30 days by 2028. For a team whose code is written and shipped by agents, the question is whether the path from report to shipped fix, including review and release, fits inside that window while reports arrive faster than they used to.

## 2. Codex keeps project config and MCP servers off in untrusted directories, even with workspace-write

**[Codex rust-v0.169.0](https://github.com/openai/codex/releases/tag/rust-v0.169.0)** · OpenAI · GitHub release notes, November 13, 2026

The release notes list it under bug fixes: "`codex exec` keeps project configuration and MCP servers disabled in untrusted directories, even with `--sandbox workspace-write`." Saving trust for a project now takes an explicit `--trust` flag on `codex exec` or `codex review`. The same release says that "Yes, clear context and implement" now passes the full approved plan to the fresh session, and keeps the current session open if that handoff fails.

**Why it matters:** Headless runs often start in a fresh checkout that Codex has never been told to trust. After this release, a sandbox flag does not load that checkout's project configuration or MCP servers. Pipelines that need them have to pass `--trust` deliberately, which also makes the decision visible in the command line.

---

## Also this cycle

- **[opencode v2.3.0](https://github.com/anomalyco/opencode/releases/tag/v2.3.0)** · opencode release notes, November 13, 2026 · Subagents now always run in the background, return their session ID at once, and report to the parent when they go idle. A subagent that goes idle with background work still running now says so in its report, so the parent waits for the final answer rather than taking the partial one as done.
- **[Lovable: Many Apps Built on the Platform Expose Sensitive Data](https://www.crissyfield.de/research/lovable-en/)** · Crissy Field GmbH, with Handelsblatt · Of 159,041 Lovable projects found in Common Crawl, 34,545 used Supabase. The firm retrieved records containing email addresses from 7,403 of 24,664 sites it examined more closely, and found cases including more than 1,000 identity document records and more than 200,000 chat messages. The authors say the 30% figure is not a confirmed leak rate, and that they did not examine Lovable's own database features.
