[GHSA-36p3-wjmg-h94x] Remote Code Execution in Spring Framework - #9585
Open
levpachmanov wants to merge 1 commit into
Open
levpachmanov wants to merge 1 commit into
levpachmanov wants to merge 1 commit into
Conversation
github-actions
Bot
changed the base branch from
main
to
levpachmanov/advisory-improvement-9585
September 16, 2026 15:11
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.
Updates
Comments
CVE-2022-22965 is a bug in Spring's bean data binding, and the entire upstream fix is one file in one module: commit
002546b3changes onlyspring-beans/src/main/java/org/springframework/beans/CachedIntrospectionResults.java, which compiles intospring-beans.jarand nothing else. The other four listed coordinates ship none of it —spring-webmvc-5.2.19.RELEASE.jarandspring-webflux-5.2.19.RELEASE.jarcontain onlyorg/springframework/web/**with zero entries underorg/springframework/beans/, and the two Boot starters contain no classes at all. The harm is a false negative on the remediation advice: the advisory tells aspring-webmvcuser the issue is"fixed": "5.2.20.RELEASE", but that jar is not meaningfully different from5.2.19.RELEASEfor this CVE — Spring version-bumps every module in lockstep. Anyone who upgrades only the coordinate the advisory named, while an olderspring-beansstays resolved through a dependency-management pin or a transitive path, reads as remediated and is still exploitable. Removing the four coordinates costs no detection coverage, because each declaresorg.springframework:spring-beansas a non-optionalcompile-scope dependency (verified in the published POMs for 4.3.30.RELEASE, 5.2.19.RELEASE and 5.3.17) — every affected project still gets flagged, now against the artifact that actually has to change.