Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-7fxc-486f-32q9

Spring HATEOAS Collection+JSON/UBER deserializers do not honor Jackson configuration

CVSS 7.5 HighEPSS 0.0028 · 20th percentile

Published by the GitHub Advisory Database at 9 Jun 2026, 06:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.hateoas:spring-hateoasMaven>=3.0.0, <3.0.4 || >=2.5.0, <2.5.3 || >=2.3.0, <=2.3.4 || <=1.5.6 || >=2.4.0, <=2.4.13.0.4, 2.5.3
Identifiers
GHSA-7fxc-486f-32q9 · CVE-2026-41006
Weakness (CWE)
CWE-284
Tags
Published
9 Jun 2026
Updated
29 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring HATEOAS versions 1.5.6 and earlier, 2.3.0 through 2.4.1, 2.5.0 through 2.5.2, and 3.0.0 through 3.0.3 are affected. The Collection+JSON and UBER deserializers bind properties via reflection without honoring Jackson access-control annotations, so an attacker who can send crafted input to these deserializers may be able to set properties that should be restricted. The source gives few details on the exact impact. Upgrade spring-hateoas to 3.0.4 or 2.5.3, depending on your release line.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.