spring-projects / spring-projects/spring-ai

No vuln-free 1.1.X release due to https://www.cve.org/CVERecord?id=CVE-2026-35568

Open
#6,960 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: waiting-for-triage
Dominant language
Java
Stars
9.5k
Forks
2.9k
Avg merge
1d 7h
Merged PRs (30d)
6

Description

1.1.X currently depends on MCP 0.18.3

I don't believe the CVE above is fixed until MCP 1.0.0, which we can't easily force to due to other breaking changes.

Net result in no vuln-free 1.1.X release.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the 1.1.X dependency configuration that brings in MCP 0.18.3, then compare it with the CVE-2026-35568 advisory and MCP 1.0.0's breaking changes. Determine whether a vulnerable-free 1.1.X dependency path is possible without those changes; done means documenting the supported release outcome or identifying the required dependency update.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring
Domain
release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.