June 08, 2026

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Betroffene Kennungen: CVE-2026-43303, CVE-2026-43492, CVE-2026-43496, CVE-2026-43499, CVE-2026-43503. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

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

Apigee X Announcement On June 8th, 2026, we released an updated version of Apigee (1-17-0-apigee-9). Note: Rollouts of this release began today and may take four or more business days to be completed across all Google Cloud zones. Your instances may not have the features and fixes available until the rollout is complete. Security

Bug ID Description

514384893 Security fix for Apigee. Hardened the Script policy to block server-side request forgery (SSRF) to link-local addresses.

N/A Security fix for Apigee infrastructure.

Fixed

Bug ID Description

512850756 Added observability metrics for the OpenTelemetry trace export pipeline, reporting spans exported, export latency, batch size, and dropped spans.

515039499 Fixed an issue where OpenTelemetry trace export over HTTP could fail to authenticate when sent through a forward proxy that requires basic authentication.

Apigee hybrid Announcement v1.16.5 On June 8, 2026 we released an updated version of the Apigee hybrid software, v1.16.5.

For information on upgrading, see Upgrading Apigee hybrid to version v1.16.5. For information on new installations, see The big picture.

Note: This is a patch release: The container images used in patch releases are integrated with the Apigee hybrid Helm charts. Upgrading to a patch via the Helm chart automatically updates the images. No manual image changes are typically needed. For information on container image support in Apigee hybrid releases, see Apigee release process. Security Various security and CVE fixes are included in this release. App Hub Feature App Hub support for …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen (CVE-2026-43303, CVE-2026-43492, CVE-2026-43496, CVE-2026-43499, CVE-2026-43503): Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://docs.cloud.google.com/release-notes#June_08_2026
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.