Security News

Cybersecurity news aggregator

HIGH Vulnerabilities SC Media

Google Cloud Vertex AI SDK flaw allowed model hijacking and code execution

A vulnerability in the Google Cloud Vertex AI SDK for Python, dubbed "Pickle in the Middle," allowed attackers to hijack model uploads by preemptively creating a Cloud Storage bucket with a predictable name when a user did not specify one. This enabled the attacker to replace the uploaded model with a malicious version; when loaded by Vertex AI, the model could execute arbitrary code, such as stealing OAuth tokens from the serving container. Google addressed the flaw by adding ownership verification and random identifiers to bucket names in SDK versions 1.144.0 and 1.148.0.
Read Full Article →

Cloud Security Google Cloud Vertex AI SDK flaw allowed model hijacking and code execution June 17, 2026 Share By SC Staff (Credit: Andreas Prott – stock.adobe.com) A vulnerability in the Google Cloud Vertex AI SDK for Python would have allowed attackers to hijack machine learning model uploads and execute code within Google's serving infrastructure. Palo Alto Networks Unit 42 discovered the flaw, dubbed "Pickle in the Middle," and reported it through Google's bug bounty program. Google has since patched the vulnerability, urging users to update their SDKs, with further coverage provided by The Hacker News. The attack exploited a weakness in how the SDK selected temporary Cloud Storage buckets for model uploads. If a user did not specify a bucket, the SDK generated a predictable name based on the project ID and region. An attacker could preemptively create this bucket in their own project. Consequently, the victim's SDK would upload model files to the attacker's bucket, allowing the attacker to replace the model with a malicious version. Many Python machine learning models use libraries like pickle or joblib, which can execute arbitrary code upon loading. When Vertex AI loaded the swapped model, the attacker's code ran within the serving container. The exploit involved a race condition, with the attacker needing to replace the model within approximately 2.5 seconds of the victim's upload. The payload could steal OAuth tokens from the serving container's metadata server, potentially granting access to other model artifacts, BigQuery metadata, and internal system information within the same Google-managed tenant project. The attack required specific conditions: the victim's default staging bucket not existing in the region and the developer not explicitly setting a staging bucket parameter. Google addressed the issue by adding ownership verification and random identifiers to bucket names in SDK versions 1.144.0 and 1.148.0. Source: The Hacker News An In-Depth Guide to Cloud Security Get essential knowledge and practical strategies to fortify your cloud security. Learn More SC Staff Related API security Security researcher reportedly accesses FIFA World Cup broadcast controls via API flaw SC Staff June 16, 2026 The researcher, known as BobDaHacker, said they exploited a flaw in FIFA's back-end API by registering as a player agent. Cloud Security ServiceNow says security researchers, not hackers, accessed data Steve Zurier June 10, 2026 ServiceNow investigates access issue, says no attacker activity found. API security Magecart campaign exploits Stripe API for credit card theft SC Staff June 5, 2026 The sophisticated attack utilizes Google Tag Manager (GTM) and Stripe domains, which are implicitly trusted by e-commerce sites, allowing the malicious code to bypass security measures. Related Events Cybercast Cloud Security: The AI Effect and How to Proceed On-Demand Event Get daily email updates SC Media's daily must-read of the most current and pressing daily news Business Email By clicking the Subscribe button below, you agree to SC Media Terms of Use and Privacy Policy . Subscribe Related Terms Cloud Computing Greynet You can skip this ad in 5 seconds

Share this article