Spring Hateoas
Approved changes feed: RSS · Atom
cpe:2.3:a:spring:spring_hateoas:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Spring (4c7a31af-cbd7-516f-b1ce-2d5f574797bc) |
|---|---|
| Product | Spring Hateoas (e6c3fad5-85fe-5df7-a524-e236a02ffa0a) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-41007 |
vulnerable | 2026-07-29 00:49:30.844295 |
Spring HATEOAS heap exhaustion through unbounded internal caching
HIGH (7.5)
Spring HATEOAS maintains an unbounded static cache of StringLinkRelation instances keyed on attacker-supplied strings.
Affected versions:
Spring HATEOAS 1.5.0 through 1.5.6; 2.3.0 through 2.3.4; 2.4.0 through 2.4.1; 2.5.0 through 2.5.2; 3.0.0 through 3.0.3.
Published: 2026-06-09T04:00:47.095Z
Updated: 2026-06-27T21:09:10.034Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-41006 |
vulnerable | 2026-07-29 00:49:30.844091 |
Spring HATEOAS Collection+JSON/UBER deserializers do not honor Jackson configuration
HIGH (7.5)
Spring HATEOAS's internal PropertyUtils.createObjectFromProperties method, used by the Collection+JSON and UBER media type deserializers, performs bean property binding via reflection without consulting Jackson access-control annotations.
Affected versions:
Spring HATEOAS 1.5.0 through 1.5.6; 2.3.0 through 2.3.4; 2.4.0 through 2.4.1; 2.5.0 through 2.5.2; 3.0.0 through 3.0.3.
Published: 2026-06-09T03:57:39.106Z
Updated: 2026-06-27T21:08:31.486Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-34036 |
vulnerable | 2026-06-08 06:06:24.246799 |
Forwarded header exploit with Spring HATEOAS on WebFlux
MEDIUM (5.3)
Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server.
For the application to be affected, it needs to satisfy the following requirements:
* It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses.
* The application infrastructure does not guard against clients submitting (X-)Forwarded… headers.
Published: 2023-07-17T10:00:43.245Z
Updated: 2024-10-30T14:52:30.766Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.