Next.js 16.3.7 is not the security release. Two labs landed on $2 and $10 a day apart.

Anthropic released Claude Sonnet 5.5 on 28 September at $2 input and $10 output per million tokens, with cache reads at $0.20, against Sonnet 4.5 at $3 and $15 with cache reads at $0.30. OpenAI released GPT-6.1 Sol on 29 September at the same $2 and $10, with cached input at $0.10, a fifth of GPT-6 Astra at $10 and $50. The Anthropic migration guide adds a caveat the price table does not: Sonnet 5.5 uses Sonnet 5's tokenizer, and against Sonnet 4.6, Sonnet 4.5 and Haiku 4.5 the same text produces about 30 percent more tokens, depending on the content. A 2000x1500 image costs about 2.5 times as many tokens, because 5.5 uses the high resolution image tier.

On 29 September Mistral's changelog announced that Leanstral 1.5 and OCR 4.0 were deprecated and retired on 30 September 2026, one day later, with Z.ai GLM 5.2 following on 31 October. On 30 September, according to TechCrunch, Reddit said it will retire RSS feeds on 13 November 2026 and close remaining public API access in March 2027, with third-party app and bot developers required to register before 12 January 2027. Reddit is quoted saying "We know RSS has been a beloved part of the open web for a long time". Separately, Reve says that after 27 September 2026 creating new images and videos is no longer available, with asset downloads until 31 October, and Google is reported to be retiring Gemini Gems on 17 November in favour of a skills format.

Vercel published 16.3.7 on 29 September. Its release notes say it is "backporting bug fixes" and list one change to the Turbopack backend, with no security content. The security release followed on 30 September: "Updates are now available in v16.3.8 (Active LTS) and v15.5.27 (Maintenance LTS)". The pre-announcement carries two dated notes, one saying 16.3.7 "does not include the security fixes planned for September 30", and one saying the release "now addresses seven vulnerabilities instead of nine. The remaining two (one critical, one high) are pending upstream coordination". The headline fix is CVE-2026-94483, server-side request forgery in Image Optimization, rated high at CVSS 8.3. The release notes for 15.5.27 list only three of the seven, so the 15.5 line does not get the SSRF fix.

LiteLLM published three advisories. The critical one, GHSA-7hp6-4w63-5g45 at CVSS 9.9, says "An authenticated user with internal_user privileges can escalate to proxy_admin and achieve remote code execution." The root cause is that "The proxy uses one encryption key for two purposes: sealing secrets at rest and minting session tokens", so a user can have the proxy encrypt forged admin metadata and present it back as a bearer token. Patched in 1.100.4, 1.101.3, 1.102.2, 1.103.1 and 1.104.0rc2. A high severity issue published 1 October, GHSA-g5ff-637f-6q2m at CVSS 8.1, lets an authenticated user read arbitrary local files through a vertex_ai_credentials alias the blocklist missed, fixed in 1.95.0, and the advisory says "There is no reliable configuration workaround on affected versions." A moderate reflected XSS in the SSO debug callback is fixed in 1.85.0. None has a CVE assigned.

CISA added CVE-2026-102489 and CVE-2026-102490 to its Known Exploited Vulnerabilities catalogue on 2 October with a remediation deadline of 5 October. The first is a session fixation issue that "can lead to remote code execution as the zammad user", the second an improper privilege management issue that "can allow the local zammad user to escalate privileges to root", and CISA notes each can be chained with the other. The Dutch security organisation DIVD says its own systems were reached on 21 September through the pair, in its words allowing "session hijacking, remote code execution and privilege escalation from the Zammad user to root, in seconds". DIVD gives the remotely exploitable range as Zammad 6.3.0 to 6.5.4, and Zammad staff on the project forum say exploitation is only possible on 6.5 and older and that 7.0 and later are not affected by the remote execution issue.

Research from UpGuard dated 1 October says it "gathered ~300,000 unique domains with indicators of Supabase usage" and "identified 16,326 databases exposing readable tables", with "over half of the databases" showing indicators of some PII and a smaller share including passwords or authentication tokens. UpGuard attributes the exposure to application-side configuration rather than a product flaw, noting that "Tables created programmatically through the API, which is how coding agents interact with Supabase, do not enable RLS by default", alongside policies that do not adequately restrict access and public keys used in client code as if they were secret. It credits Supabase with having "made product changes to implement RLS by default for tables created in the Table Editor UI". Supabase's chief information security officer Bil Harmer told TechCrunch the company provides "secure defaults and tooling, and customers control how their own projects are configured".

OpenAI released GPT-6.1 Sol on 29 September "for complex coding and professional work at a lower cost than GPT-6 Astra". Standard pricing for prompts up to 272K input tokens is "$2 input, $0.10 cached input, $2.50 cache write, and $10 output" per million, against Astra at $10 input, $1 cached and $50 output. The context window is 1,050,000 tokens with 128,000 maximum output and an April 2026 knowledge cutoff. The same day OpenAI added computer use to the Agents API, where "Agents can complete tasks in an OpenAI-hosted browser, with website access approvals and sign-in handled by your application", and an Ultrafast mode for GPT-6 Astra through service_tier, which the changelog says has global processing and US data residency and does not support EU or other regional inference residency.

Cloudflare moved AI Search to general availability on 1 October. The changelog says "Usage-based billing begins on November 1, 2026, with included monthly ingestion, storage, semantic query, and full-text query usage", without publishing rates or the size of those allowances. Cloudflare says it will email a reminder the week before. A quieter change sits in the same entry: Workers AI embedding and reranking calls made by AI Search are now included in AI Search pricing, and "These calls no longer appear on your Workers AI bill or in your AI Gateway logs." Artifacts, described as a versioned file system that speaks Git, entered open beta the same day for Workers Paid customers, with billing starting 14 October 2026.

Restate announced a $20M Series A led by Singular, with Redpoint Ventures and Capital One Ventures participating. It sells durable execution infrastructure that keeps multistep processes consistent across crashes and network interruptions, and co-founder Stephan Ewen is quoted saying "You need to make sure you track exactly what you do to make it reproducible and have a consistent outcome." The company built its own storage, replication and redundancy layers rather than depending on an external database, and names Replit as a customer. For context, Temporal raised $550M at a $12.55B valuation on 18 September.

Article 50(2) of the EU AI Act requires providers of systems generating synthetic audio, image, video or text content to ensure "that the outputs of the AI system are marked in a machine-readable format and detectable as artificially generated or manipulated". Chapter IV, which contains it, has applied since 2 August 2026. The Digital Omnibus on AI, Regulation (EU) 2026/1744, added a new Article 111(4) giving a transitional period to providers of such systems "that have been placed on the market before 2 August 2026", who must comply "by 2 December 2026". The same regulation deferred the high risk obligations to 2 December 2027 for Annex III systems and 2 August 2028 for Annex I. The marking duty does not apply "to the extent the AI systems perform an assistive function for standard editing or do not substantially alter the input data provided by the deployer or the semantics thereof", or where authorised by law for criminal investigation.

Anthropic announced on 30 September that claude-sonnet-4-5-20250929 is deprecated, "with retirement on the Claude API scheduled for November 30, 2026", recommending claude-sonnet-5-5 as the replacement. That is roughly 60 days of notice, matching Anthropic's stated policy, and requests to a model past its retirement date fail. The deprecation page adds an important scope note: "The dates on this page apply to Anthropic-operated platforms: the Claude API, Claude Platform on AWS, and Microsoft Foundry. Partner-operated platforms (Amazon Bedrock and Google Cloud) set their own retirement schedules, so a model's lifecycle status and dates can differ."

GitHub announced on 1 October that "The macOS 14 runner image will be retired on November 2, 2026", covering the labels macos-14, macos-14-large and macos-14-xlarge. Eight brownout windows precede it, during which jobs using macOS 14 "will temporarily fail", the first running from "October 5, 14:00 UTC to October 6, 00:00 UTC". GitHub also warns it "may reduce macOS 14 runner capacity, which could result in longer queue times" before retirement. The replacements it lists are all described as "macOS arm64 labels": macos-latest, which is macos-26, plus macos-15, macos-latest-xlarge and macos-15-xlarge.

Supabase's breaking change entry says new tables in the public schema will no longer be exposed to the Data API by default, "enforced on all projects on 2026-10-30". The dashboard control is named "Automatically expose new tables and functions". The entry is explicit that row level security is not the mechanism here: "Without an explicit GRANT, a role will not have access to the created table." It advises bundling GRANT statements alongside the ENABLE ROW LEVEL SECURITY and policy statements in the same migration if you use a custom migration framework.

Stripe released API version 2026-09-30.endive on 30 September with an unusually broad set of breaking changes. Passing payment_method_types when creating a Checkout Session "now returns a 400 error", and the parameter is removed from Payment Intents and Setup Intents too, with excluded_payment_method_types and a new allowed_payment_method_types named as replacements. In Stripe.js, setting paymentMethodTypes means "Stripe.js now throws an integration error and prevents the Elements instance from being created or updated", and elements.create for the payment request button now throws, with the Express Checkout Element as the replacement. Behaviour also changed where it still works: allowed_payment_method_types "silently filters out incompatible methods" where the old parameter returned an error. Stripe publishes no end-of-life date for older API versions.

Apple posted on 1 October that "The original Developer ID Certification Authority (Sub-CA) expires on February 1, 2027. Certificates issued by this authority will stop working on that date." The consequence is stated plainly: "Starting February 1, 2027, .pkg files signed with an affected certificate will no longer install." The remedy is to generate a replacement from the current authority, Developer ID Certification Authority (G2), which Apple says "is valid until 2031, but the certificates issued by the certificate authority expire annually and must be renewed each year".