Bump spring-boot from 4.0.5 to 4.0.6 (CVE-2026-40976)

[Copilot]

Spring Boot 4.0.0–4.0.5 contains a critical vulnerability where the default security filter chain provides no authorization, exposing all endpoints to unauthenticated access under specific conditions.

Change

• Bumped spring-boot from 4.0.5 → 4.0.6 in gradle/libs.versions.toml

Reachability

Not reachable — high confidence. The vulnerability requires actuator-autoconfigure present, no custom Spring Security config, and no spring-boot-health. This repo has none of these — it's a validation library with no actuator dependency, no SecurityFilterChain, and no deployable web application surface. Update is to clear the scanner alert.

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Spring Boot's default security filter chain has no authorization rule with Actuator but without Health</alert_title>
<alert_description>In certain circumstances, Spring Boot's default web security is ineffective allowing unauthorized access to all endpoints. For an application to be vulnerable, it must: be a servlet-based web application; have no Spring Security configuration of its own and rely on the default web security filter chain; depend on spring-boot-actuator-autoconfigure; not depend on spring-boot-health. If any of the above does not apply, the application is not vulnerable.

Affected: Spring Boot 4.0.0–4.0.5; upgrade to 4.0.6 or later per vendor advisory.</alert_description>

critical
GHSA-8v8j-3hxp-93wr, CVE-2026-40976
org.springframework.boot:spring-boot
maven
<vulnerable_versions>= 4.0.5</vulnerable_versions>
<patched_version>4.0.6</patched_version>
<manifest_path>settings.gradle</manifest_path>

https://nvd.nist.gov/vuln/detail/CVE-2026-40976 https://spring.io/security/cve-2026-40976 https://github.com/advisories/GHSA-8v8j-3hxp-93wr

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking changes that are found. If the package manager fails to resolve dependencies (e.g. peer dependency conflicts, incompatible engine constraints), document the error in the PR description rather than attempting increasingly complex workarounds. After updating, check the lock file to confirm the package no longer resolves to a version in the vulnerable range. Keep changes minimal and tightly scoped. Ensure tests, build, type checking, and linting all pass after your changes. If there are any test, lint, or typechecking failures, investigate whether they are caused by the update and fix them if so — do not leave broken tests in the PR. If they were already present before the update, note them in the PR description so a human reviewer can assess whether they are related.</task_instructions>

• Resolves getyourguide/openapi-validation-java alert v1.2.7 #47

[Copilot]

Pull request overview

Updates the Gradle version catalog to use Spring Boot 4.0.6 in response to CVE-2026-40976 / GHSA-8v8j-3hxp-93wr (primarily to clear vulnerability scanner findings).

Changes:

• Bump Spring Boot from 4.0.5 to 4.0.6 in the version catalog.
• Update/rewrites gradlew.bat (appears unrelated to the Spring Boot bump and may be an accidental formatting/EOL-only change).

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated 2 comments.

File	Description
gradlew.bat	Included in the PR as a full-file change; likely an unintended rewrite/normalization that adds noise.
gradle/libs.versions.toml	Bumps spring-boot version to 4.0.6.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.