CVE-2025-13426

Improper Sandboxing in Google Apigee's JavaCallout Policy Allows for Remote Code Execution

HIGH

8.7

CVSS Score

Published: December 5, 2025 at 09:27 PM UTC

Updated: September 25, 2026 at 11:27 PM UTC

1 product affected across 1 vendorApigee hybrid

Using Apigee hybrid Javacallout policy by Google Cloud?

Get instant alerts when new vulnerabilities affect Apigee hybrid Javacallout policy - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH8.7

Exploit prediction

EPSS 0.4%

SSVC

No known exploit

Description

A vulnerability exists in Google Apigee's JavaCallout policy https://docs.apigee.com/api-platform/reference/policies/java-callout-policy that allows for remote code execution. It is possible for a user to write a JavaCallout that injected a malicious object into the MessageContext to execute arbitrary Java code and system commands at runtime, leading to unauthorized access to data, lateral movement within the network, and access to backend systems. The Apigee hybrid versions below have all been updated to protect from this vulnerability: * Hybrid_1.11.2+ * Hybrid_1.12.4+ * Hybrid_1.13.3+ * Hybrid_1.14.1+ * OPDK_5202+ * OPDK_5300+

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Apigee hybrid · Google Cloud

60%

v < Hybrid_1.11.2v < Hybrid_1.12.4v < Hybrid_1.13.3v < Hybrid_1.14.1v < OPDK_5202v < OPDK_5300

Affected range stops below Hybrid_1.11.2, so it looks safe — our inference, not a vendor statement

Affected range stops below Hybrid_1.12.4, so it looks safe — our inference, not a vendor statement

Affected range stops below Hybrid_1.13.3, so it looks safe — our inference, not a vendor statement

Affected range stops below Hybrid_1.14.1, so it looks safe — our inference, not a vendor statement

Affected range stops below OPDK_5202, so it looks safe — our inference, not a vendor statement

Affected range stops below OPDK_5300, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (1)

Source: cverecord

https://docs.cloud.google.com/apigee/docs/hybrid/release-notes#March_01_2025

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHGoogleCloud

Vector?

Quick Info

StatusDEFERRED

CWE

CWE-913

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card