Rather a little late but I encountered the exact same behavior today (migrating from Jackson 2.17 to 2.18).

Was able, with some effort, to figure out the issue and a clean solution.

Jackson, not being able to find the constructor, is very clearly the root cause. And I'm inclined to believe the problem occurs in the specific scenario of multiple existing constructors.

The clean and very straightforward solution is to add the @JsonCreator annotation for each constructor Jackson will be using. Somehow it was decided this annotation is required as of 2.18 while it was not required before.