The RustSec advisory explicitly lists both functions in its 'Affected Functions' section for versions <2.3.0. The vulnerability stems from incomplete body consumption before processing subsequent requests, which would occur in these core request handling functions. The release notes confirm decode() had breaking changes to fix the issue, while accept() remained the primary API entrypoint. Both functions are directly involved in request processing and would be responsible for proper body consumption.