NGINX fixes five flaws, three scored 9.2
NGINX 1.30.6 and 1.31.7 close three 9.2 memory bugs, a TLS client-certificate bypass and an HTTP/3 injection path. None is known exploited, and each needs a specific configuration to reach.
Archive
NGINX 1.30.6 and 1.31.7 close three 9.2 memory bugs, a TLS client-certificate bypass and an HTTP/3 injection path. None is known exploited, and each needs a specific configuration to reach.
Agents now call agents over MCP. Each hop forwards instructions the origin never saw, and tool registries keyed by name are a spoofing surface. The boundary has to move from the model to the protocol.
A practical pipeline for catching malicious dependencies before they run: pin with a lockfile, block install scripts, verify provenance where it exists, and diff dependencies on every pull request.
This week: why agent security is an authorization problem, a gateway review you can run before the next deploy, and the first hour of a package incident.
Open weights remove a license fee, not the operating cost. The decision hinges on utilization, latency, privacy and the team you can staff.
A gateway centralizes model access, but it also centralizes credentials, data and failure. Use this checklist before it becomes the single point of compromise.
A six-month path from Linux and networking to a platform you can operate. Ordered by dependency, not by hype.
Once a model can call tools, the interesting asset is no longer the prompt. It is the identity, the data in context, and the actions you forgot to scope.
Static output hides the complexity in the build. The sites that age well treat the pipeline as a product: pinned, cached, observable and reproducible.
General-purpose AI obligations began applying in August 2025. If you buy or deploy a model, the documentation you can obtain is now part of your risk assessment.