Skip to content

Bump starlette in v1 to fix CVE-2026-48710 #6038

Closed

Description

@lucasoshiro

🔴 Required Information

Currently, ADK v1 requires starlette prior to version 1, which contains the vulnerability reported in CVE-2026-48710. It was already fixed in v2 (#5894) but not in v1.

Describe the Bug:
ADK v1 depends on an outdated version of starlette that needs to be bumped to address CVE-2026-48710.

Activity

  1. added
    web[Component] This issue will be transferred to adk-web
    on Jun 9, 2026
  2. added theissue type on Jun 9, 2026
  3. surajksharma07 commented on Jun 10, 2026

    @surajksharma07
    Collaborator

    /adk-issue-analyze

  4. surajksharma07 commented on Jun 10, 2026

    @surajksharma07
    Collaborator

    @lucasoshiro Thanks for catching this — you're right that the fix in #5894 only landed on main, leaving v1 users still exposed.

    As a quick mitigation, try adding starlette>=1.0.1 to your project's requirements and confirm that clears the vulnerability on your end.

    We'll work on getting the same bump applied to the v1 branch — appreciate the detailed CVE context!

  5. lucasoshiro commented on Jun 10, 2026

    @lucasoshiro
    Author
  6. mikerepede commented on Jun 17, 2026

    @mikerepede

    Things have gotten even worse in the past couple days. There are 2 more high severity CVEs:

    1. CVE-2026-48818 (requires starlette v1.1.0)
    2. CVE-2026-54283 (requires starlette v1.3.1)

    @surajksharma07 What is the outlook for getting this fix applied to ADK v1? Thanks!

  7. lucasoshiro commented on Jul 11, 2026

    @lucasoshiro
    Author

    Hi @surajksharma07 and @mikerepede !

    I opened this PR changing the version of starlette: #6378

  8. surajksharma07 commented on Jul 13, 2026

    @surajksharma07
    Collaborator

    @lucasoshiro Thanks for opening #6378 — checked the diff and it only bumps starlette to 1.0.1, which closes the original CVE-2026-48710 but not the two @mikerepede flagged: CVE-2026-48818 needs >=1.1.0 and CVE-2026-54283 needs >=1.3.1, so v1 would still be exposed to both of those right after this merges.

    Could you bump the lower bound to >=1.3.1 instead so all three close together?

    Separately — main/v2's pyproject.toml is still pinned at starlette>=1.0.1,<2 too, so this same gap needs a follow-up bump there as well, independent of this issue!

    Team is looking more into it.
    Thanks!

  9. added a commit that references this issue on Jul 16, 2026
    221bad9
  10. dcsullivanMT commented on Jul 17, 2026

    @dcsullivanMT

    I would like to request that this issue be reopened. Although the PR was merged, the necessary Starlette version bump has not yet been reflected in a v1 release. As this issue specifically concerns ensuring the v1 branch is protected, it should remain open until the fix is released for v1.

  11. itworsley commented on Jul 21, 2026

    @itworsley

    Would like to second @dcsullivanMT's request here. This is becoming a blocker/severe risk for those not yet ready to update ADK to v2

  12. added a commit that references this issue on Aug 11, 2026
    6c754f2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

request clarification[Status] The maintainer need clarification or more information from the authorweb[Component] This issue will be transferred to adk-web

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions