Google Cloud Apigee Hybrid up to 1.11.1/1.12.3/1.13.2/1.14.0 Javacallout Policy dynamically-managed code resources

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.00

Summaryinfo

A vulnerability has been found in Google Cloud Apigee Hybrid up to 1.11.1/1.12.3/1.13.2/1.14.0 and classified as very critical. Affected by this issue is some unknown functionality of the component Javacallout Policy. Performing a manipulation results in dynamically-managed code resources. This vulnerability was named CVE-2025-13426. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as very critical, was found in Google Cloud Apigee Hybrid up to 1.11.1/1.12.3/1.13.2/1.14.0. This affects an unknown part of the component Javacallout Policy. The manipulation with an unknown input leads to a dynamically-managed code resources vulnerability. CWE is classifying the issue as CWE-913. The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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+

The weakness was presented by Nikita Markevich. The advisory is shared at docs.cloud.google.com. This vulnerability is uniquely identified as CVE-2025-13426 since 11/19/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/06/2025).

Upgrading to version 1.11.2, 1.12.4, 1.13.3 or 1.14.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-201493). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Dynamically-managed code resources
CWE: CWE-913
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Apigee Hybrid 1.11.2/1.12.4/1.13.3/1.14.1

Timelineinfo

11/19/2025 CVE reserved
12/06/2025 +17 days Advisory disclosed
12/06/2025 +0 days VulDB entry created
12/06/2025 +0 days VulDB entry last update

Sourcesinfo

Advisory: docs.cloud.google.com
Researcher: Nikita Markevich
Status: Confirmed

CVE: CVE-2025-13426 (🔒)
GCVE (CVE): GCVE-0-2025-13426
GCVE (VulDB): GCVE-100-334533
EUVD: 🔒

Entryinfo

Created: 12/06/2025 04:55
Updated: 12/06/2025 07:44
Changes: 12/06/2025 04:55 (69), 12/06/2025 07:44 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!