Remove transitive vulerability to LiteLLM via upgrade of google-cloud-aiplatform#64786
Merged
eladkal merged 1 commit intoapache:mainfrom Apr 7, 2026
Conversation
4f64888 to
6d48c72
Compare
eladkal
approved these changes
Apr 7, 2026
shivaam
pushed a commit
to shivaam/airflow
that referenced
this pull request
Apr 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
To remove potential vulnerability as google-cloud-ai-platform optionally sources litellm, upgrade dependency to google package which prevents the vulnerable version to be used.
Unfortunately I see no other way to enforce this as the transitive dependency is optional only and enforcing a specific version is only possible if we make the optional dependency mandatory.
Unfortunately the google package only upper bounds the version to the last non-vulnerable version, hoping for an improvement as litellm==1.83.0 should actually fix it.
PMC Only, see https://github.com/apache/airflow/security/dependabot/537
Google PR: googleapis/python-aiplatform#6484
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.