Adobe Premiere Pro Update Addresses 1 Vulnerability
Tech GuruQuick Answer
Adobe Premiere Pro 26.5 and 25.6.6 fix CVE-2026-84395, a server-side request forgery issue that Adobe classifies as security-feature bypass. The affected branches end at 26.3.2 and 25.6.5. Adobe rates the issue Critical, assigns update priority 3, and says it is unaware of exploitation in the wild.
Confirm Scope And Apply The Supported Fix
What to do now: Record the installed Premiere branch and deploy 26.5 or 25.6.6 through Adobe's supported updater. Coordinate project, plugin and export checks before returning workstations to production.
Last verified: 2026-09-23 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.
Scope And Authority
| Product scope | Adobe Premiere Pro |
|---|---|
| Advisory | APSB26-157 |
| CVE | CVE-2026-84395 |
| Adobe bulletin publication | 2026-09-22 (Adobe bulletin) |
| Recorded source timestamp (historical snapshot) | 2026-09-22 18:58:12.860 UTC |
| Affected versions | Premiere Pro 26.3.2 and earlier, and 25.6.5 and earlier |
| Fixed version | Premiere Pro 26.5 or 25.6.6 |
| CVSS base score | 7.1 (CVSS v3.1) |
| CVSS severity | Critical |
| Exploitation status | Adobe states that it is not aware of exploitation; no exploitation claim is inferred. |
What Changed
The bulletin identifies SSRF (CWE-918) with a CVSS 3.1 score of 7.1. Its vector specifies local access and no user interaction; it does not name the affected endpoint or establish an internet-reachable unauthenticated service. Do not expand the stated security-feature bypass into a code-execution claim.
What To Validate Now
- Inventory. Locate Adobe Premiere Pro deployments, versions, enabled features, exposure paths, owners, and dependent services.
- Establish applicability. Compare each deployment with the authority's affected-version statement: Premiere Pro 26.3.2 and earlier, and 25.6.5 and earlier Do not infer applicability from product family or severity alone.
- Remediate. Apply Premiere Pro 26.5 or 25.6.6 through the supported vendor or project channel, following the current advisory and change-control requirements.
- Validate. Confirm the fixed version after restart and test approved project loading, media access, plugins and exports on Windows or macOS as applicable. Keep production project backups and record regressions separately from security update completion.
- Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.
Operational Cautions
Use the exact supported release stream and repository. Test dependencies, clusters, integrations, and rollback before broad deployment; a CVSS rating or reachable feature is not evidence of exploitation.
Evidence To Retain
- Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
- UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
- Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.
Related TechGeeks Resources
Authoritative References
Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.
