Security Resilience

CWE · MITRE source

CWE-488Exposure of Data Element to Wrong Session

Abstraction: Base · CVEs in our corpus: 47

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.

Data can "bleed" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool. In the case of Servlets, developers sometimes do not understand that, unless a Servlet implements the SingleThreadModel interface, the Servlet is a singleton; there is only one instance of the Servlet, and that single instance is used and re-used to handle multiple requests that are processed simultaneously by different threads. A common result is that developers use Servlet member fields in such a way that one user may inadvertently see another user's data. In other words, storing user data in Servlet member fields introduces a data access race condition.

Last updated: 14 October 2026 20:41 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.AA-05
  • PR.DS-10
  • PR.IR-01
  • SC-4 Information in Shared System Resources
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2026-164987.410.00.00462026-07-28
CVE-2026-163267.410.00.00542026-07-29
CVE-2026-19931 7.49.80.00752026-09-06
CVE-2024-27455 6.99.10.00642024-02-26
CVE-2025-47928 6.99.10.00632025-05-15
CVE-2024-38367 6.88.20.11132024-07-01
CVE-2025-1247 6.48.30.00822025-02-13
CVE-2026-864926.38.50.00902026-09-07
CVE-2024-6162 6.27.50.01702024-06-20
CVE-2026-80231 6.07.50.00902026-09-06
CVE-2023-6519 5.97.50.00512024-02-08
CVE-2024-5148 5.97.50.00572024-09-02
CVE-2026-5773 5.97.50.00662026-05-13
CVE-2025-30073 5.87.50.00372025-03-26
CVE-2023-1907 5.78.00.00452025-01-09
CVE-2026-343915.77.50.00262026-03-27
CVE-2026-824165.77.70.00232026-10-13
CVE-2026-543115.67.70.00392026-06-23
CVE-2024-27935 5.57.20.00722024-03-21
CVE-2026-18489 5.57.40.00262026-09-04
CVE-2026-880175.57.30.00232026-09-10
CVE-2024-41977 5.47.10.00442024-08-13
CVE-2026-54497 5.26.80.00332026-07-17
CVE-2022-40210 5.16.80.00202023-05-10
CVE-2026-23646 5.16.50.00372026-01-19