The vulnerability stems from a pattern-matching conflict between Apache Shiro (using AntPathMatcher) and Spring Boot 2.6+ (using PathPatternParser by default). Shiro's AntPathMatcher#match function is directly responsible for evaluating security constraints against request paths using Ant-style syntax. When Spring Boot uses a different parsing strategy (PathPattern), the same URL may be interpreted differently at the routing layer (Spring) versus the security layer (Shiro), creating mismatches that allow bypass. The function is explicitly implicated because the mitigation requires either aligning Spring's matcher with Shiro's AntPathMatcher or updating Shiro to handle this conflict.