Spring Cloud Stream EUVD-2026-67194

Exploitation requires the attacker to hold high-privilege credentials (PR:H per CVSS), meaning control over the application layer, its messaging infrastructure, or an administrative account - not an anonymous or low-privileged network position. User interaction is also required (UI:R), further preventing fully automated or opportunistic exploitation and demanding either social engineering or participation by an authenticated user in the triggering action. High attack complexity (AC:H) implies additional preconditions such as specific gadget classes being present on the application classpath or a particular message deserialization code path being reachable. Exploitation is bounded by unchanged scope (S:U), and the C:L/I:L impact ceiling rules out full system compromise or availability disruption. Deployments where incoming message types are strictly controlled via allowlisting or where the messaging infrastructure is isolated from untrusted inputs are at materially lower risk.

Converging signals consistently place this in the low-priority tier. The CVSS base score of 3.1 is grounded in a tightly constrained vector: high attack complexity (AC:H), high privileges required (PR:H), mandatory user interaction (UI:R), and bounded impact of only C:L and I:L with no availability dimension. No EPSS data was provided in the source intelligence, and the vulnerability does not appear in CISA KEV, nor is any public proof-of-concept exploit known. The 'deserialization' tag may initially raise alarm given that class's historical association with remote code execution, but the C:L/I:L impact ratings explicitly rule out full system compromise in this scenario - suggesting type confusion outcomes are limited in scope rather than leading to arbitrary code execution. The PR:H requirement means this is not exploitable by an external unauthenticated attacker; an adversary would need existing elevated access to the application or its messaging infrastructure, making this largely a privilege-escalation or lateral-movement concern within an already-compromised environment rather than an initial-access vector. Overall, this is a routine patch-cycle item: apply the vendor fix at the next scheduled maintenance window with no urgent emergency response warranted.

An attacker who already holds high-privilege access to the Spring Cloud Stream environment - for example, write access to a Kafka or RabbitMQ topic the application consumes - could craft a message payload containing a maliciously typed serialized Java object and publish it to the message channel. Exploitation would then depend on a user-initiated action that triggers the application to deserialize the payload, after which the attacker could read or manipulate a limited subset of application data. No public proof-of-concept exploit has been identified at time of analysis, making opportunistic exploitation unlikely.