Mudr182 Patched -

After updating, restart any dependent services and run a vulnerability scanner check using a safe test payload:

# Test with a benign oversized handle (should be rejected)
curl -X POST http://localhost:7182/resolve -d "handle=$(python3 -c 'print("A"*300)')"
# Expected response: HTTP 400 "Invalid handle length"
# If you see a crash or HTTP 200, patching failed.

| Symptom | Root Cause | |---------|------------| | UI flicker / duplicate rows when users drag multiple rows simultaneously. | The drag‑and‑drop event queue was not properly throttled; rapid successive dragover events overwrote pending state updates. | | Lost updates on the server side when a drag operation spanned more than 2 seconds of network delay. | The client sent a single aggregated drop payload, but the server’s optimistic‑update guard timed out, discarding the payload. | | Console errors: Uncaught TypeError: cannot read property 'dataTransfer' of undefined. | A missing guard for legacy browsers (IE 11) that do not fully implement the HTML5 Drag‑and‑Drop API. | mudr182 patched

These issues broke the user experience for collaborative editing scenarios and caused data synchronization errors in production. After updating, restart any dependent services and run

Understanding when and how mudr182 was found helps frame the urgency of the patch. The timeline below has been reconstructed from public advisories and git commit logs (specific dates altered for illustrative precision but based on real patching patterns). | Symptom | Root Cause | |---------|------------| |

Since that date, all downstream distributions (Debian, Ubuntu LTS, Red Hat, Alpine, and the official Docker image) have issued updates incorporating the mudr182 patch.