Repository navigation
Stored ZIP entries can report successful completion despite truncated data #134496
Description
Activity
Tagging subscribers to this area: @karelz, @dotnet/area-system-io-compression
See info in area-owners.md if you want to be subscribed.- added a commit that references this issue
on Sep 25, 2026
For stored ZIP entries, the archive metadata can declare a compressed size that is smaller than the entry's uncompressed size. In this scenario, the reader may reach EOF before consuming the expected amount of data and still report successful completion.
This behavior is inconsistent with the documented completed-read validation contract. A fully drained entry read can succeed even though the entry data is truncated and CRC validation is never performed.