Text of github.com › curl › curl › issues › 24006 as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Stale mid reuse in multi notification queue (wrong-transfer callback) · Issue #24006 · curl/curl · GitHub

Skip to content You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert Stale mid reuse in multi notification queue (wrong-transfer callback) #24006 New issue Copy link New issue Copy link Closed Closed Stale mid reuse in multi notification queue (wrong-transfer callback) #24006 Copy link Labels libcurl API vuln:NONE Vulnerability assessed and deemed insignificant Vulnerability assessed and deemed insignificant Description Shaunak-Chatterjee opened on Nov 17, 2026 Issue body actions I did this Summary CURLM_NTFY queue entries store only e->mid .

Between enqueue ( Curl_mntfy_add ) and deferred dispatch (end of perform/socket cycle), an easy handle can be removed and its mid re-issued to a NEW transfer once the 25%-free slack is consumed. Curl_multi_get_easy() then resolves the stale mid to the NEW easy, delivering WRONG callbacks with a valid-but-wrong CURL*. Apps freeing per-transfer state in the callback free the wrong object. Exploitation Needs churn-heavy app: repeated add/remove inside notify cbs is explicitly allowed (api.c:81 allow_ntfy_cb).

An attacker scripting an app driving mass handle rotations (crawler/proxy) can trigger this during load; deterministic crash or double-free. Novelty API added in 2025-2026 (multi_ntfy rework). No public report. The table mid-reuse is documented-by-design ("OS pid reuse analogy") but the deferred-queue poisoning angle is not covered. Remediation Store dense generation counter (mid, gen) per notification, or curl_multi_remove_handle purges pending notifications for that mid, or Lookup through GOOD_EASY_HANDLE magic validation before callback.

RT-08_Multi_MID_Reuse_Notify_Stale.md I expected the following No response curl/libcurl version curl / libcurl 8.23.1-DEV (commit 307f084 ) operating system Mac OS Tahoe Activity bagder added libcurl API vuln:ASSESS Vulnerability problem? If so, what severity? Vulnerability problem? If so, what severity? on Nov 17, 2026 bagder commented on Nov 17, 2026 bagder on Nov 17, 2026 Member More actions repeated add/remove inside notify cbs This sounds like a bug that is unlikely to trigger and that cannot be forced by an attacker. bagder added vuln:NONE Vulnerability assessed and deemed insignificant Vulnerability assessed and deemed insignificant and removed vuln:ASSESS Vulnerability problem?

If so, what severity? Vulnerability problem? If so, what severity? on Nov 17, 2026 icing commented on Nov 17, 2026 icing on Nov 17, 2026 Contributor More actions Proposing to fix this via #24014 bagder closed this as completed in ab8cd2b on Nov 17, 2026 opensource-fork-sync added a commit that references this issue on Nov 17, 2026 multi_ntfy: remove transfers on multi remove This issue will close once commit ab8cd2b is merged into the 'master' branch. ab8cd2b Sign up for free to join this conversation on GitHub.

Already have an account? Sign in to comment Metadata Metadata Assignees No one assigned Labels libcurl API vuln:NONE Vulnerability assessed and deemed insignificant Vulnerability assessed and deemed insignificant Type No type Projects No projects Milestone No milestone Relationships None yet Development No branches or pull requests Issue actions You can’t perform that action at this time.