Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
cve-2026-59273-spring-security-elmatcher — CVE-2026-59273 - Spring Security - Critical 9.8 - Remote - SpEL injection. ELRequestMatcher bound from external input evaluates with type access on 7.1.2; the same expression is refused on 7.1.3. Differential harness, inert payloads, no execution chain. | Kitploit
Tools/GitHubGitHub/abraxas/cve-2026-59273-spring-security-elmatcher
Vulnerability AnalysisCode AnalysisExploitationWeb SecurityLearning & Education
GitHubabraxas/cve-2026-59273-spring-security-elmatcher

cve-2026-59273-spring-security-elmatcher

CVE-2026-59273 - Spring Security - Critical 9.8 - Remote - SpEL injection. ELRequestMatcher bound from external input evaluates with type access on 7.1.2; the same expression is refused on 7.1.3. Differential harness, inert payloads, no execution chain.

View Repository
118h 49m agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    911
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    707
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    431
  • 4

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    405
  • 5

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    352
  • 6

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    342

Explore all tools

Browse our collection of tools

View all tools →
Share

Abraxas Labs - CVE-2026-59273

CVE-2026-59273

Spring Security's ELRequestMatcher evaluates its expression in an unrestricted StandardEvaluationContext, which allows type references and static method access. Spring's data binding will turn a supplied string into one of these matchers, so an application that binds outside input onto a RequestMatcher-typed property hands the expression evaluator a string it did not write.

Class: Expression injection reachable through data binding Reach: Remote, on applications that bind external input to a RequestMatcher

Spring Security 7.1.0 - 7.1.2, 7.0.0 - 7.0.8, 6.5.0 - 6.5.12, 6.4.0 - 6.4.19, 5.8.0 - 5.8.28, 5.7.26 and earlier

IDCVE-2026-59273
ClassExpression injection (SpEL)
ReachRemote, conditional on application binding
CWECWE-94 / CWE-95 / CWE-470
CVSSCritical: 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (vendor)
ProductSpring Security
Affected7.1.2 and the ranges above
Fixed7.1.3, 7.0.9 open source; commercial patches for 6.x and 5.x
LicenseGNU Affero GPL v3.0
LabJDK 17+, Maven, no server and no Docker

What this harness proves

Spring's BeanWrapperImpl accepts a plain string for a RequestMatcher property and produces an ELRequestMatcher. On the vulnerable line, that matcher evaluates the string in a StandardEvaluationContext, which permits type references and static access. On the patched line the same expression is refused, because the context became SimpleEvaluationContext.forReadOnlyDataBinding().withInstanceMethods().

The differential is the finding. Three payloads separate what each context allows:

Payload7.1.27.1.3Why
1 + 1 == 2matchesmatchesArithmetic is allowed in both contexts
'witness'.toUpperCase() == 'WITNESS'matchesmatcheswithInstanceMethods() survives the patch
T(java.lang.Math).abs(-1) == 1matchesSpelEvaluationExceptionType references are refused by SimpleEvaluationContext

The third row is the discriminator. The second row matters for testing: a regression test that only exercises an instance method will pass on both versions and prove nothing.

What this harness does not prove

Every payload is inert. There is no T(...) on a process class, no Runtime, no ProcessBuilder, and no class loader work. Math.abs is the deepest call in the repository. This is a reachability test, not a weaponised chain: it demonstrates that the evaluator runs with type access on the vulnerable line and without it on the patched line. It does not carry that to command execution.

That distinction is the point of the artifact. It is the regression test the fix should ship with, and it is safe to run on a build machine.

What an attacker can do

PositionMethod / sinkRecon / integrity / availabilityProven or inferred
Application binds outside input to a RequestMatcher propertyBeanWrapperImpl#setPropertyValue -> ELRequestMatcher(String)Integrity (control flow)Lab-proven. The bound value becomes ELRequestMatcher
The bound expression runs on request matchingELRequestMatcher#matches -> Expression#getValueIntegrityLab-proven. typeref.matched=true on 7.1.2
The expression reaches types and static methodsStandardEvaluationContextIntegrityLab-proven. T(java.lang.Math) resolves
Same expression on the patched lineSimpleEvaluationContextn/aLab-proven. SpelEvaluationException
Read application data through reflectiontype accessConfidentialityInferred from type access. Not exercised here
Invoke a processtype accessAvailabilityInferred from the advisory. Not exercised here
Reach an application that never binds input to a matchern/an/aClosed. The jar alone is not reachable

Stays closed

AxisWhy it is closed
Unauthenticated reach without a binding siteThe precondition is a property of the application, not the library
Command execution in this repositoryNo process payload exists here, by design
The patch allowing the same expression7.1.3 refuses the type reference outright

How I found it

The advisory attributes discovery to a property editor registered by naming convention. On both releases the JDK lookup returns nothing:

editor=none

The bind still succeeds, through the ELRequestMatcher(String) constructor that Spring's type conversion finds. That is the narrower thing to audit: an application is exposed when outside input can reach a RequestMatcher-typed property, not when a PropertyEditor happens to be registered. Both halves point at the same sink, and the constructor is the one that fires on a stock classpath.

The patch is visible in the bytecode rather than in behaviour alone:

$ javap -p -c -classpath spring-security-web-7.1.2.jar ...ELRequestMatcher
  createELContext
     0: new  #50  // class org/springframework/expression/spel/support/StandardEvaluationContext

$ javap -p -c -classpath spring-security-web-7.1.3.jar ...ELRequestMatcher
  createELContext
     0: invokestatic  #50  // SimpleEvaluationContext.forReadOnlyDataBinding
     3: invokevirtual #56  // SimpleEvaluationContext$Builder.withInstanceMethods

withInstanceMethods() is still on the builder, which is why instance methods keep working after the fix and why the type reference is the only reliable probe.

The lab

python3 cve-2026-59273-spring-security-elmatcher-Abraxas-Labs.py

or directly:

cd lab && ./run.sh

The runner resolves both pins from Maven Central, compiles once per version, and prints one RESULT line each. It exports -Djava.net.preferIPv4Stack=true, because some networks hand the JVM an AAAA record with no working IPv6 route and Maven then reports No route to host.

# vulnerable 7.1.2
RESULT label=7.1.2 elMatcher=yes editor=none arith.matched=true instance.matched=true typeref.matched=true
# patched 7.1.3
RESULT label=7.1.3 elMatcher=yes editor=none arith.matched=true instance.matched=true typeref.matched=false typeref.error=SpelEvaluationException

Recorded on JDK 27.0.1 with Maven 3.10.0, macOS arm64.

Other affected lines:

VULN=7.0.8 FIXED=7.0.9 ./run.sh

The fix

Upgrade to 7.1.3 or 7.0.9. On Spring Boot 4.x, 4.1.3 or 4.0.10 pulls the corresponding Spring Security. Releases 6.5.13, 6.4.20, 5.8.29, and 5.7.27 are commercial support only, so installs on those lines stay exposed until they have a support agreement. There is no configuration workaround in the advisory.

If you cannot upgrade, do not bind external input onto a RequestMatcher-typed property. That binding is the whole reachability condition.

References

  • Spring Security advisory
  • ELRequestMatcher on 7.1.3
  • CWE-94

License

Abraxas Labs - [email protected]

Download Tool