CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-45074 remediation guide

symfony symfony, security-http

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 7.1.0 until 7.4.12 and 8.0.12, Cas2Handler builds the CAS service parameter from Request::getSchemeAndHttpHost(), which reflects an attacker-controlled Host header when framework.trusted_hosts is not configured; an attacker controlling another application registered with the same CAS server can replay a victim ticket against the Symfony application and authenticate as the victim. This issue is fixed in versions 7.4.12 and 8.0.12.

Open CVE record
Productsymfony symfony, security-http
Affected versions>= >= 7.1.0-BETA1, < 7.4.12, >= >= 8.0.0-BETA1, < 8.0.12, >= 7.1.0 < 7.4.12, >= 8.0.0 < 8.0.12
Fixed versions7.4.12, 8.0.12
Priority basisReview · CVSS 7.6 · EPSS 0.41%
01

Identify the affected asset

Confirm whether symfony symfony, security-http is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= >= 7.1.0-BETA1, < 7.4.12, >= >= 8.0.0-BETA1, < 8.0.12, >= 7.1.0 < 7.4.12, >= 8.0.0 < 8.0.12. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 7.4.12, 8.0.12. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.