Skip to content
VulniPulse
High8.1Red Hat Linux

High [CVE-2026-47864] org.springframework.integration/spring-integration-http: Spring Integration: Arbitrary code execution via unsafe Java deserialization

This high-severity Red Hat Linux advisory covers CVE-2026-47864 affecting Red Hat Fuse 7.

CVE-2026-47864 Published Aug 27, 2026Updated by vendor Aug 27, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in Spring Integration. The SerializingHttpMessageConverter component deserializes incoming HTTP request bodies without proper class filtering.

A remote, unauthenticated attacker can exploit this by sending a specially crafted HTTP request. If a known Java deserialization 'gadget' is present on the application's classpath, this can lead to arbitrary code execution.

When processing HTTP requests with Content-Type application/x-java-serialized-object, the converter invokes ObjectInputStream.readObject() on the request body without class filtering or type validation. A remote, unauthenticated attacker can supply a malicious serialized payload.

Red Hat severity: Important — CVSS 8.1 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-502.

Affected Red Hat products: Red Hat Fuse 7. Red Hat does not currently list a fixing RHSA for this CVE.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Do not accept application/x-java-serialized-object content types on HTTP inbound endpoints, or configure custom HttpMessageConverter instances that enforce explicit ObjectInputFilter allowlists before deserialization occurs.

Official advisory · high-confidence parse· fetched 2 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.