Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-59283 – SpEL Safety Guard Bypass (Compiler) – Spring Framework 5.2.x–7.0.8

Be the first to know when new zero-days emerge:

Summary

CVE-2026-59283 is a safety-guard bypass vulnerability in the Spring Expression Language (SpEL) implementation of Spring Framework. It affects applications that evaluate SpEL expressions using SimpleEvaluationContext while the SpEL expression compiler is active, allowing the compiler to silently compile expressions and bypass the safety restrictions that SimpleEvaluationContext is meant to enforce during interpreted evaluation. The vulnerability has a CVSS v3.1 base score of 9.1 (Critical) with a network attack vector.

Technical details

  • Root cause: when the SpEL expression compiler is active, expressions evaluated through SimpleEvaluationContext can be silently compiled into generated bytecode; the compiled form does not re-apply the restricted-evaluation safety guards enforced during normal interpreted evaluation.
  • Trigger conditions: the application must (1) evaluate SpEL expressions via SimpleEvaluationContext, and (2) have the SpEL compiler enabled, either via the spring.expression.compiler.mode property/system property set to IMMEDIATE or MIXED, or via a SpelParserConfiguration created with SpelCompilerMode.IMMEDIATE or MIXED.
  • Attack vector: network — any input path that reaches SpEL evaluation restricted by SimpleEvaluationContext (e.g., user-supplied expressions in application logic) can be leveraged once compilation is enabled.
  • Impact: bypass of SpEL’s restricted evaluation safety guards, and unbounded class-loading growth, since each distinct compilable expression generates and loads a new class into a child ClassLoader, which can also lead to resource exhaustion.

Affected software

  • Spring Framework 7.0.0 – 7.0.8
  • Spring Framework 6.2.0 – 6.2.19
  • Spring Framework 6.1.0 – 6.1.28
  • Spring Framework 6.0.0 – 6.0.30
  • Spring Framework 5.3.0 – 5.3.49
  • Spring Framework 5.2.25.RELEASE and earlier

Severity

CVSS v3.1 Base Score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: upgrade to Spring Framework 7.0.9 (available in open source). Fixes for 6.2.20, 6.1.29, 6.0.31, 5.3.50, and 5.2.26 are available only under Spring Enterprise Support.
  • If no patch can be applied: avoid enabling the SpEL compiler (spring.expression.compiler.mode = IMMEDIATE/MIXED, or SpelCompilerMode.IMMEDIATE/MIXED via SpelParserConfiguration) in combination with SimpleEvaluationContext. Fixed versions disable compilation by default in SimpleEvaluationContext; if compilation is required for performance reasons, it must be explicitly re-enabled via the withCompilationSupported() builder method, with the understanding that doing so removes the safety guards.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Response body: Caused by: org.springframework.data. or at: org.springframework.data., org.springframework.data.mapping.MappingException, org.springframework.data.repository.RepositoryCreationException, /WEB-INF/lib/spring-data-commons-<version>.jar, spring-data-commons-<version>.jar, /META-INF/MANIFEST.MF followed by spring-data-commons

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge