Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GHSA-8v8j-3hxp-93wr / GHSA-wwpq-f5c3-7hvx: Dependabot incorrectly flags spring-boot 4.1.0 as vulnerable

Open
#8,085 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
spring-boot
Domain
security

Research direction

Start by locating the records for GHSA-8v8j-3hxp-93wr and GHSA-wwpq-f5c3-7hvx, then trace how their vulnerable ranges are represented and compared with Spring Boot versions. Determine whether the advisory data or comparison behavior causes 4.1.0 to be flagged; done means the alert no longer applies to 4.1.0 and the affected range remains accurate.

Written by the indexing model from the issue text.

Description

Summary

Dependabot is generating alerts for org.springframework.boot:spring-boot:4.1.0 against both GHSA-8v8j-3hxp-93wr and GHSA-wwpq-f5c3-7hvx.

Problem

Both advisories explicitly define the vulnerable range as >= 4.0.0, < 4.0.6 for the 4.x branch.

4.1.0 > 4.0.6 — it is mathematically outside the vulnerable range. Spring Boot 4.1.0 was released after 4.0.6 and includes the fixes for both CVEs.

The advisory descriptions confirm this:

  • GHSA-8v8j-3hxp-93wr: "Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later"
  • GHSA-wwpq-f5c3-7hvx: "Spring Boot 4.0.0–4.0.5 (fix 4.0.6)"

Impact

Repositories using Spring Boot 4.1.0 (the latest release) receive incorrect CRITICAL and HIGH Dependabot alerts for vulnerabilities that do not affect them.

Expected behaviour

Dependabot should not flag spring-boot:4.1.0 since 4.1.0 >= 4.0.6.

Suggestion

If the advisory is correct as written and the scanner is the bug, please fix the version comparison logic.
If 4.1.x is also affected (which the advisory text contradicts), please add a separate vulnerable range >= 4.1.0, < 4.1.x with an explicit patched version.

Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 18h
Merged PRs (30d)
48

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.

More from github/advisory-database

All issues in github/advisory-database

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.