Skip to content
OpenAdvisories

Weakness (CWE)

CWE-488: Exposure of Data Element to Wrong Session

Base Draft

The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.

How to prevent it (3 mitigations)
  1. Architecture and Design

    Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.

  2. Testing

    Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).

  3. Architecture and Design

    In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.

Source: MITRE CWE-488

2 results · Clear filters · Feed

  • Medium 6.5
    CVE-2026-85296 Public exploit

    Apache Camel: Camel-AS2 Cross-Partner Signing Key Confusion via Shared Per-Request State

    Exposure of Data Element to Wrong Session vulnerability in Apache Camel AS2 component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. Signing material belonging to an individual request was stored in state that is shared…

  • Medium 5.9
    CVE-2026-85245 Public exploit

    Apache Camel: Camel-Thrift Cross-Exchange Data Disclosure via a Shared Deserialization Target

    Exposure of Data Element to Wrong Session vulnerability in Apache Camel Thrift component. This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1. The Thrift data format unmarshalled incoming data into the shared defaultInstance o…