Meilisearch 1.55 fixes ranking-threshold slowdowns and blocks a vector-index corruption path
A search-engine maintenance release carries intentional relevance and API compatibility changes that operators should test.
Search
Search results for “package-manager vulnerability scanning”
Find published research by company, product, platform or technology.
Showing 21–40 of 165 dossiers
Web DevelopmentMarketing & DistributionWordPressDeveloper ToolsMarketplaces & PlatformsActive dossier
WordPress.org can now stop high-risk plugin updates before they reach sites
The important change is enforcement. WordPress.org already had a release cooldown and automated scanning, but high-risk results can now stop a plugin update automatically instead of waiting for the Plugins Team to intervene.
Artificial IntelligenceWeb DevelopmentJavaScriptAI CodingBrowsers & Web StandardsDeveloper ToolsActive dossier
Google's AI bug hunter finds different V8 flaws from fuzzing — Project Zero says keep both
A six-month real-world comparison shows AI code-review agents and specialised fuzzers find substantially different V8 vulnerabilities. Replacing fuzzing with agents would leave gaps, and cost per bug remains unknown.
PostgreSQL JDBC 42.7.14 closes authentication and SQL-data leakage flaws
Two pgJDBC vulnerabilities affect different older driver ranges and only specific connection or binary-write configurations. Upgrade and verify the affected paths rather than treating this as a PostgreSQL server vulnerability.
Gemini CLI 0.60 hardens the boundaries around extensions, sandboxes and MCP OAuth
This is not one headline vulnerability fix. Gemini CLI 0.60 is a coordinated hardening pass across the plumbing that lets extensions, sandboxes, filesystem paths and MCP authentication influence an agent’s execution environment.
Elementor Pro’s unauthenticated file-upload flaw is now being actively exploited
The important development is active exploitation, not the original vulnerability disclosure. WordPress operators running Elementor Pro 4.2.1 or earlier should treat this as an immediate patch-and-hunt event, especially on sites with public forms that include optional file uploads.
Chrome patches a V8 zero-day already being exploited in the wild
This is not a speculative browser bug. The vulnerable code sits in Chrome’s JavaScript and WebAssembly engine, exploitation is confirmed, and the remediation boundary is concrete: desktop Chrome needs the September 3 patched build or later.
WordPress 7.0.4 fixes an Author-level file upload path to remote code execution
WordPress 7.0.4 fixes CVE-2026-65640, a CVSS 8.8 remote code execution flaw affecting installations that process malicious PostScript uploads through Imagick and Ghostscript. Fixes have also been backported to branches as old as 4.7.
GitHub Copilot Projects gives coding agents persistent goals across repositories
Copilot Projects can coordinate agents, files and recurring tasks across repositories or non-code work; review and permissions remain human responsibilities.
Coolify 4.4 adds built-in traffic analytics, external secrets and OIDC to self-hosted deployments
Coolify 4.4.0 adds opt-in proxy traffic analytics, external secret managers, OIDC login, audit trails, Cloudflare DNS and experimental SQLite. Operators need to account for proxy restarts, Caddy redeploys and feature maturity.
Hugging Face releases 207 versioned WebGPU kernels for browser AI
Hugging Face has released 207 Apache-2.0 WebGPU kernels, a JavaScript loader and Fleet, a browser benchmarking service. The package makes kernel contracts and correctness evidence inspectable, but performance remains device- and workload-dependent.
TanStack AI 1.0 stabilises its provider-neutral SDK — but the agent harness is still experimental
The three-maintainer TanStack AI project has reached stable 1.0 for its core SDK, with 23 providers; its long-running agent harness is not yet stable.
GitHub makes enterprise licence compliance a pull-request merge gate — with an API for coding agents
A new GitHub ruleset can stop unapproved dependency licences at merge time, and agents can check packages before recommending them.
Video.js 10.1 adds a Scaffold skin and simpler v8 migration paths after its ground-up rewrite
The follow-up clarifies package upgrade behavior and provides a practical migration starting point for developers moving away from v8.
pg_vault_tde 1.7.2 fixes encrypted PostgreSQL corruption — but upgrades require table rewrites
The important part of pg_vault_tde's 1.7.2 release is the operational migration: v4 rows can still be read after upgrade, but UPDATE can crash until they are rewritten.
Preact 11 switches to ESM-only distribution and rewrites hydration boundaries
Preact's long-awaited major release brings concrete rendering changes and a packaging break. Most modern projects should migrate easily, but old import paths and CommonJS tooling need attention.
Pi 1.0 makes Codemode and MCP part of a stable minimal coding-agent harness
Pi’s first stable release is interesting less for another coding-agent version number than for what its deliberately minimal core now considers mature enough to include: MCP, code-driven tool orchestration and model routing.
Meta Muse turns a consumer AI assistant into a persistent agent — and its first Mac zero-day tests the containment model
Muse packages persistent autonomous execution, credentials, payments, app access and memory into a mainstream consumer product. A September macOS hotfix now provides an early real-world lesson: agent containment has to protect not only the cloud runtime but also the local control path into the agent.
Laravel Vet puts a trust gate in front of Composer dependency updates
Vet turns dependency updates from an implicit trust decision into an explicit, reviewable one for Laravel, Symfony, WordPress and plain PHP projects, with optional local coding-agent review layered underneath the human trust decision.
Azure Document Intelligence v2.0 API retires August 31 — old integrations need a version migration
Azure Document Intelligence v2.0 reaches retirement on August 31, 2026. Microsoft recommends moving workloads to the current v4.0 API; the post-v2 REST surface was redesigned, so teams should verify the actual api-version their SDK or HTTP client sends rather than assuming a package upgrade is enough.