Repository navigation
Enforce actual Imagick sequence frame limits - #21
Merged
Merged
Conversation
smnandre
force-pushed
the
security/animation-frame-limit
branch
from
September 27, 2026 13:26
e0e4410 to
a11e257
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The header's approximate frame count allowed longer sequences to bypass
maxFramesbefore Imagick decoded and coalesced them.Probe the complete sequence before pixel decoding, enforce the actual count again before coalescing, and apply a scoped native list-length limit where supported. Restore the previous native limit after both successful and failed requests, while preserving existing corrupt-input and missing-coder errors.