Spring HATEOAS allows mutation of read-only properties via Collection+JSON and UBER payloads

MEDIUM | NOVEMBER 19, 2026 | CVE-2026-59376

Description

Spring HATEOAS does not honour Jackson's @JsonProperty(access = Access.READ_ONLY) declaration when deserializing Collection+JSON (application/vnd.collection+json) and UBER (application/vnd.uber+json) request bodies.

Both media types reconstruct the domain object from the name/value pairs of the incoming representation using an internal, reflection-based property binder rather than Jackson's own bean deserializer. That binder resolves each property's setter from the JavaBeans property descriptor and invokes it directly, applying only Jackson's @JsonIgnore and @JsonIgnoreProperties exclusions. Properties declared read-only are not excluded, so a client-supplied value for such a property is accepted and written to the object.

As a result, a client able to submit a Collection+JSON or UBER request body can populate properties that the application declared as server-owned and expected to be ignored on input, such as a role, permission or account-state property. The same payload submitted as application/json is handled by Jackson's bean deserializer, which correctly ignores those properties, so the exposure is specific to the two affected media types.

Affected applications are those that enable Collection+JSON or UBER hypermedia support and bind request bodies directly onto a domain type declaring a @JsonProperty(access = Access.READ_ONLY) property with a setter. Applications using only the HAL or HAL-FORMS media types are not affected, as those do not use the affected binder on the deserialization path. Applications that bind requests onto dedicated input DTOs without read-only properties are also not affected.

Affected Spring Products and Versions

Spring HATEOAS:

  • 3.1.0 - 3.1.3
  • 3.0.0 - 3.0.6
  • 2.5.0 - 2.5.4
  • 2.0.0 - 2.4.3
  • 1.5.8 and earlier

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.
Fix versionAvailability
3.1.4OSS
3.1.3.1Enterprise Support Only
3.0.7OSS
3.0.6.1Enterprise Support Only
2.5.5Enterprise Support Only
2.4.4Enterprise Support Only
1.5.9Enterprise Support Only

Users who cannot upgrade immediately can apply one of the following:

  • Do not bind Collection+JSON or UBER request bodies directly onto domain types that carry read-only properties. Bind onto a dedicated input DTO that only declares the properties a client is allowed to supply, and map it onto the domain type in application code.
  • Alternatively, replace @JsonProperty(access = Access.READ_ONLY) with @JsonIgnore on the setter of the affected properties, which is honoured on the affected deserialization path. Note that this also removes the property from the serialized representation unless a separate accessor is exposed for output.
  • If Collection+JSON or UBER support is not required, remove the corresponding media type from the @EnableHypermediaSupport configuration.

Credit

This issue was identified and responsibly reported by Yu Bao from PayPal Cyber Security Team.

History

  • 2026-11-19: Initial vulnerability report published.

Get ahead

VMware offers training and certification to turbo-charge your progress.

Learn more

Get support

TrueSource Spring Enterprise offers support and binaries for OpenJDK™, Spring, and Apache Tomcat® in one simple subscription.

Learn more

Upcoming events

Check out all the upcoming events in the Spring community.

View all