The vulnerability manifests through stack overflow during JSON parsing of deeply nested structures, as demonstrated in the GitHub issue #54 PoC. The root cause is recursive parsing without depth limits in JSONObject initialization. While exact implementation details aren't available, the entry point through JSONObject constructor and subsequent recursive parsing logic (common in JSON parsers) would be the vulnerable path. The high confidence comes from: 1) The PoC directly triggers stack overflow via JSONObject initialization 2) The CWE-787 classification indicates memory corruption from unbounded writes, which aligns with stack overflow through uncontrolled recursion 3) The patch version 1.5.2 would logically add depth limitation checks in this parsing pathway.