Releases
v3.0.0
v3.0.0 - SSRF Security Hardening
Latest
Compare
Sorry, something went wrong.
No results found
[3.0.0] - 2026-01-30
Security
CRITICAL : Removed client-side URL fetching to prevent SSRF vulnerabilities
URLs are now passed to the server for secure server-side fetching
Restricted sign() method to local files only (API limitation)
Changed
BREAKING : sign() only accepts local files (paths, bytes, file objects) - no URLs
BREAKING : Most methods now accept FileInputWithUrl - URLs passed to server
BREAKING : Removed client-side PDF parsing - leverage API's negative index support
Methods like rotate(), split(), deletePages() now support negative indices (-1 = last page)
All methods except sign() accept URLs that are passed securely to the server
Removed
BREAKING : Removed process_remote_file_input() from public API (security risk)
BREAKING : Removed get_pdf_page_count() from public API (client-side PDF parsing)
BREAKING : Removed is_valid_pdf() from public API (internal use only)
Removed ~200 lines of client-side PDF parsing code
Added
SSRF protection documentation in README
Migration guide (docs/MIGRATION.md)
Security best practices for handling remote files
Support for negative page indices in all page-based methods
You can’t perform that action at this time.