Windows 11's Snipping Tool appears to have a bug similar to Pixel's Markup tool “aCropalypse” bug, which lets anyone reveal info edited out in some screenshots
João Carrasqueira / XDA Developers :
Context & Ripple Effects
The report followed researchers’ disclosure of the related Pixel Markup flaw, which showed that visual edits could fail to remove underlying image data in some saved files. That made a similar finding in a Windows screenshot utility a cross-platform privacy issue rather than an isolated mobile-app defect.
The immediate arc closed with updates for Windows 10 Snip & Sketch and Windows 11 Snipping Tool, while Microsoft’s earlier Snipping Tool availability problems underscore how a small built-in utility can become a broad Windows maintenance concern.
First-order effects
- People who shared affected, edited screenshots could have exposed information they believed had been removed; visual redaction was not a reliable safeguard for those files.
- Microsoft needed to correct the affected screenshot-saving behavior, a response reflected in the later Snipping Tool and Snip & Sketch fixes.
Second-order effects
- The parallel with the Pixel Markup disclosure puts pressure on image-editing toolmakers to audit how crop and redact actions alter the underlying file, not just what the interface displays.
- Organizations that use screenshots in support, reporting, or documentation may need to revise sharing practices around sensitive images until edited copies are verified.
Third-order effects
- If similar flaws recur, “redact” and “crop” features will increasingly be judged as data-deletion controls, raising the security bar for default utilities embedded in operating systems.
- The pattern favors privacy-by-design testing of file transformations before new editing and AI-assisted features are added to widely deployed desktop tools.
The trend: This is part of a broader shift toward treating everyday content-editing features as security-sensitive data-handling infrastructure, not merely convenience tools.