Node.js November security releases fix high-severity HTTP/2 and TLS flaws
Upgrade Node.js to 22.23.5, 24.22.3 or 26.13.1, rebuild runtime images, and review HTTP/2 and mutual-TLS exposure; October fixes remain relevant.
Find published research by company, product, platform or technology.
Showing 381–400 of 597 dossiers
Upgrade Node.js to 22.23.5, 24.22.3 or 26.13.1, rebuild runtime images, and review HTTP/2 and mutual-TLS exposure; October fixes remain relevant.
Oracle's Visual Builder availability change closes two hosted app-building routes to new customers, but it is not a shutdown or migration deadline for existing deployments.
YepAPI corrected a platform-wide flat-rate billing defect on August 22 and left historical undercharges untouched. On the same date it also increased selected flat-rate and volume prices, making the current cost step-up larger for some endpoints than the billing fix alone would suggest.
CircleCI has consolidated three config-breaking changes onto a September 21 cutoff. Teams using legacy v2.0 syntax, out-of-scope parameters or unsupported regex constructs need to migrate before pipelines begin failing at compilation time.
Google Play’s 2026 target-API cutoff has two separate consequences: most new submissions and updates need API 36, while existing apps below API 35 can lose distribution to new users on newer Android devices. Developers who need more time can request an extension to November 1.
DataGrip 2026.3 embeds DuckDB to run cross-database joins over existing connections, reducing ad hoc data export and ETL setup.
Brazilian customers can authorize Pix Automático mandates for Paddle subscriptions without a separate early-access application. The path broadens local-payment access for SaaS, while delayed renewals, fixed mandate amounts and re-authorisation requirements still create implementation caveats.
Theme developers using Shopify CLI 3.83.x and older against password-protected storefronts are now past the documented cutoff. Shopify requires 3.84.0 or later for these flows; the live changelog's September 23 date supersedes the earlier October 1 deadline in this dossier.
The practical change is bigger than another package-manager version. Homebrew can now tell operators whether vulnerabilities are actually outstanding in the formula revisions they installed, while its own recent advisories show why package-manager metadata, uninstall paths and build isolation deserve the same scrutiny as package contents.
The deadline is no longer theoretical: browsers, Git HTTPS backends and API clients that still depend on SHA-1-era TLS algorithms can now lose connectivity to GitHub.com.
Alpine rebuilt its GitLab after attempted exploitation and warns that upgrading GitLab alone may not patch custom containers using unpatched Ruby.
Devin Fusion's persistent lead/sidekick architecture now has newer model choices and independently reported cost/quality comparisons, changing its practical deployment economics.
Northflank clarifies the October 30 secret-exposure window and alert-to-patch timeline; an affected customer confirms database credentials were at risk, although its own logs show no unauthorised access.
A November 6 tinyjs patch repairs Windows builds broken by 0.71.0. Because affected apps cannot launch their updater, operators must rebuild and redistribute them.
OpenSSH 10.6p2 and Alpine backports address a critical musl/no-PAM password bypass; operators must restart sshd after upgrading.
ChatGPT Ads replaces new-campaign bid ceilings with Target CPA/CPC from Nov 9 and retires legacy controls Jan 1, 2027.
Kimi K3.1 Pro's full open-weight release is now public. Its 2.8T-parameter MoE has 104B active per token and a 1M-token context; local hosting requires serious infrastructure and checking Moonshot's specific licence.
Herd Studio integrates existing CLI agents with local previews, isolated workspaces and optional database clones; Laravel Cloud deployment is built into Herd 2.
The immediate follow-up to 2.11.8 restores trailing-slash PHP directory indexes and hardens FastCGI script selection and authentication boundaries.
Go developers can adopt encoding/json/v2 and jsontext for stricter JSON parsing and more flexible streaming. Behaviour differences require compatibility testing; reported speedups are project benchmarks.