The stack trace in GitHub issue #13 shows repeated calls to markNodesToPrune() causing StackOverflowError. This indicates recursive processing without depth control. The vulnerability manifests when parsing HTML with deep nesting/cyclic references, as shown in the PoC. The Debian security advisory confirms the fix involved adding nesting depth limits, which would directly impact these recursive functions. While markNodesToPrune is clearly vulnerable (high confidence), addIfNeededToPruneSet is implicated in the stack trace but with less direct evidence of being the primary recursion driver (medium confidence).