Only the latest published major version of the ImageResize NuGet package receives security fixes.
| Version | Supported |
|---|---|
| 3.x | ✅ |
| < 3.0 | ❌ |
Please do not open public GitHub issues for security problems.
Report privately via one of:
- GitHub Security Advisories: https://github.com/YodasMyDad/ImageResize/security/advisories/new
- Email: lee@aptitude.co.uk
Include:
- Affected version(s) and platform
- A minimal reproduction (PoC, command, or crafted image)
- Your assessment of impact (RCE, DoS, information disclosure, path traversal, etc.)
We aim to acknowledge reports within 3 business days and ship a fix or mitigation within 30 days for high-severity issues. You will be credited in the release notes unless you prefer to remain anonymous.
The library exposes a file-system-backed cache and decodes untrusted images. Consumers should:
- Keep
ImageResizeOptions.Boundsset to sensible values — never accept unbounded width/height from request queries. - Keep
ImageResizeOptions.MaxSourceBytesset (defaults to 256 MiB) to reject decompression bombs before they reach the decoder. - Ensure the middleware is registered before
UseStaticFiles()so resizes are not shadowed by raw file serving. - Store
CacheRooton a dedicated volume with a quota; theCache.MaxCacheBytescap is a soft limit, not a hard one. - Do not expose the cache directory over HTTP unless necessary.