Browsershot
Endless Lifecycle Support (ELS) for Browsershot from TuxCare provides security fixes for Browsershot package versions that have reached their end-of-life. This allows you to continue running your applications without vulnerability concerns, even after official support has ended.
Supported Versions and Components
- Browsershot 3.61.0, 4.4.0
Other versions upon request.
Connection to ELS for Browsershot Repository
This guide outlines the steps needed to integrate the TuxCare ELS for Browsershot repository into your application. The repository provides trusted Browsershot packages that can be easily integrated into your Composer projects.
Step 1: Get user credentials
You need a username and password in order to use TuxCare ELS for Browsershot repository. Anonymous access is disabled. To receive the credentials, please contact sales@tuxcare.com.
Step 2: Configure Composer authentication
Create or edit the
auth.jsonfile for the user running Composer:Linux/macOS:
~/.composer/auth.jsonWindows:
%APPDATA%\Composer\auth.json
Use either the Composer CLI or edit
auth.jsondirectly to add your credentials fornexus.repo.tuxcare.com.composer config --global --auth http-basic.nexus.repo.tuxcare.com USERNAME PASSWORDReplace
USERNAMEandPASSWORDwith the credentials you received in Step 1.
Step 3: Register the TuxCare repository
Add the els_php Composer repository either via CLI or by editing composer.json:
composer config repositories.tuxcare '{"type":"composer","url":"https://nexus.repo.tuxcare.com/repository/els_php/","options":{"http":{"verify":true}}}' --jsonStep 4: Install Browsershot
Install the TuxCare-maintained Browsershot release that matches your project:
composer require spatie/browsershot:3.61.0-p1+tuxcareCheck the exact version listed in your TuxCare Nexus account to ensure you receive the most recent patched release.
If you edited composer.json manually, run composer update to install the package:
composer update
Composer will resolve dependencies against the TuxCare repository and install the patched releases.
Composer Repository Configuration
If you encounter dependency resolution errors like:
packages from higher priority repository do not match your constraint
it usually means your project requires a package version that is not yet available in the TuxCare repository.
Solution: Update your composer.json to set the TuxCare repository as non-canonical:
{
"repositories": [
{
"type": "composer",
"url": "https://nexus.repo.tuxcare.com/repository/els_php/",
"canonical": false
}
]
}
This allows Composer to fall back to Packagist for packages not available in the TuxCare repository, while still preferring TuxCare patches when available.
Vulnerability Exploitability eXchange (VEX)
VEX is a machine-readable format that tells you if a known vulnerability is actually exploitable in your product. It reduces false positives and helps prioritize real risks.
TuxCare provides VEX for Browsershot ELS versions: security.tuxcare.com/vex/cyclonedx/els_lang_php/spatie-browsershot/
How to Upgrade to a Newer Version
If you have already installed a TuxCare Browsershot package and want to upgrade to a newer release, update the version string in your composer.json file or run the composer require command with the new version:
composer require spatie/browsershot:VERSION-pN+tuxcare
Then run composer update to apply the changes:
composer update
Resolved CVEs
Fixes for the following vulnerabilities are available in ELS for Browsershot from TuxCare:
| CVE ID | Severity | Vulnerable versions | Fixed in version |
|---|---|---|---|
| CVE-2025-3192 | High | 3.61.0 | 3.61.0-p2+tuxcare |
| CVE-2025-1026 | High | 3.61.0 | 3.61.0-p1+tuxcare |
| CVE-2024-21547 | High | 3.61.0 | 3.61.0-p1+tuxcare |
| CVE-2024-21549 | High | 3.61.0 | 3.61.0-p1+tuxcare |
| CVE-2024-21544 | High | 3.61.0 | 3.61.0-p1+tuxcare |
| CVE-2025-1022 | High | 3.61.0 | 3.61.0-p1+tuxcare |
If you are interested in the TuxCare Endless Lifecycle Support, contact sales@tuxcare.com.