CVE REMEDIATION GUIDE
Priority reviewHighFixed-version data available

CVE-2026-35029 remediation guide

BerriAI litellm, Red Hat Ansible Automation Platform 2.6, Red Hat OpenShift AI 2.25

LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, the /config/update endpoint does not enforce admin role authorization. A user who is already authenticated into the platform can then use this endpoint to modify proxy configuration and environment variables, register custom pass-through endpoint handlers pointing to attacker-controlled Python code, achieving remote code execution, read arbitrary server files by setting UI_LOGO_PATH and fetching via /get_image, and take over other privileged accounts by overwriting UI_USERNAME and UI_PASSW...

Open CVE record
ProductBerriAI litellm, Red Hat Ansible Automation Platform 2.6, Red Hat OpenShift AI 2.25
Affected versions>= < 1.83.0, < 1.83.0
Fixed versions1.83.0
Priority basisPriority · CVSS 8.7 · EPSS 26.4%
01

Identify the affected asset

Confirm whether BerriAI litellm, Red Hat Ansible Automation Platform 2.6, Red Hat OpenShift AI 2.25 is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= < 1.83.0, < 1.83.0. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

FIRST EPSS indicates an elevated probability of exploitation. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 1.83.0. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2026-35029 Remediation Guide | SECUFOCUS NOW