June 18, 2026

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Betroffene Kennungen: CVE-2025-13462, CVE-2026-41567, CVE-2026-41568, CVE-2026-415687, CVE-2026-42306. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

API Gateway Change Update to the API Gateway runtime architecture The API Gateway runtime architecture is being updated to improve its integration with Google Cloud Platform and its services. This update does not affect existing API Gateway features. However, be aware of the following differences:

Status code changes for gRPC API Gateways

Error New status code Previous status code

Quota exceeded ResourceExhausted Unavailable

Invalid API key InvalidArgument InternalError

For 4xx client-side quota failures, API Gateway will now reject requests (fail closed). This applies to both gRPC and OpenAPI API Gateways.

If you experience any other differences in behavior due to this update, contact Google Cloud Customer Care. Note: Rollouts of this release to production instances might take up to 4 weeks to complete across all Google Cloud zones. Your instances might not be updated until the rollout is complete. Agent Registry Announcement Agent Registry is generally available (GA). The following are features available in Agent Registry for the GA launch stage:

API v1 and client libraries: The v1 version of the Agent Registry API is available. Cloud client libraries are available in C#, Go, Java, Node.js, PHP, Python, and Ruby. A2A v1 support: Agent Registry supports Agent-to-Agent (A2A) protocol version 1.0, letting you explicitly declare transport endpoints and bindings inside the supportedInterfaces array, in addition to the existing 0.3 schema support. Terraform support: Terraform scripts for Application Default Credentials (ADC) have graduated to General Availability. You …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen (CVE-2025-13462, CVE-2026-41567, CVE-2026-41568, CVE-2026-415687, CVE-2026-42306): Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://docs.cloud.google.com/release-notes#June_18_2026
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.