With NestedIOException already removed in the Spring Framework 6 milestone, we should signal to the community that they should no longer rely on this exception. NestedIOException is an IOException so users should rather catch that if they have to.