LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI
Description
LiteLLM through 2026-04-08 allows remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI
Remediation
Apply vendor security updates immediately. Monitor for exploitation attempts and review access logs.
---METADATA---
VENDOR: Axios
PRODUCT: Axios
AFFECTED_VERSIONS: Prior to 1.15.0
---END_METADATA---
Description Summary:
Axios is vulnerable to a prototype pollution attack chain that can be escalated to remote code execution or AWS IMDSv2 bypass.
Executive Summary:
A critical vulnerability in the Axios library allows for prototype pollution to be escalated into remote code execution or full cloud environment compromise.
Vulnerability Details
CVE-ID: CVE-2026-40175
Affected Software: Axios
Affected Versions: Prior to 1.15.0
Vulnerability: This vulnerability involves a "Gadget" attack chain where prototype pollution is leveraged to achieve remote code execution or bypass AWS IMDSv2 protections. The vulnerability is accessible to external attackers through the HTTP client's processing of malicious data.
Business Impact
With a CVSS score of 10.0, this is a maximum-severity flaw. The impact ranges from full server takeover to the compromise of cloud infrastructure, potentially allowing attackers to escalate privileges and access sensitive cloud metadata, leading to widespread data breaches.
Remediation Plan
Immediate Action: Update the Axios library to version 1.15.0 or later across all applications and dependencies.
Proactive Monitoring: Utilize Software Composition Analysis (SCA) tools to identify and track the usage of vulnerable Axios versions throughout the development lifecycle.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block malicious payloads associated with prototype pollution techniques.
Exploitation Status
Public Exploit Available: No
Analyst Notes: As of April 10, 2026, there is no public information indicating active exploitation of this vulnerability. However, due to the nature of the flaw, the potential for exploitation is high.
Analyst Recommendation
The severity of this vulnerability necessitates an immediate update. Development teams must ensure that all instances of Axios are patched to the secure version to prevent potential cloud-level compromises.