How severe is GHSA-j8gj-9rm5-4xhx?

No CVSS score has been assigned to GHSA-j8gj-9rm5-4xhx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j8gj-9rm5-4xhx?

GHSA-j8gj-9rm5-4xhx affects the following packages: symfony/security-http (Packagist), symfony/security-http (Packagist), symfony/symfony (Packagist), symfony/symfony (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-j8gj-9rm5-4xhx?

Update symfony/security-http to 7.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8gj-9rm5-4xhx is resolved across your whole dependency graph.

How do I detect GHSA-j8gj-9rm5-4xhx in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j8gj-9rm5-4xhx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-j8gj-9rm5-4xhx actively exploited in the wild?

No public exploit code has been indexed for GHSA-j8gj-9rm5-4xhx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j8gj-9rm5-4xhx?

GHSA-j8gj-9rm5-4xhx has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 40th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-j8gj-9rm5-4xhx?

GHSA-j8gj-9rm5-4xhx is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j8gj-9rm5-4xhx published, and has it been updated?

GHSA-j8gj-9rm5-4xhx was published on May 27, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

Symfony's Cas2Handler Derives CAS service URL from Client Host Header → Cross-Service Ticket ReplayGHSA-j8gj-9rm5-4xhx

Fix: symfony/symfony@5ba145d

GHSA-j8gj-9rm5-4xhx is a CWE-290 vulnerability in symfony/security-http. A fix is available for symfony/security-http — see the affected versions and patch details below.

Also known asCVE-2026-45074

Published

May 27, 2026

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-j8gj-9rm5-4xhx.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs40th percentile — riskier than 40% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

4 pkgs affected

🐘symfony/security-http🐘symfony/security-http🐘symfony/symfony🐘symfony/symfony

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Cas2Handler builds this service parameter from Request::getSchemeAndHttpHost(), which reflects the attacker-controlled HTTP Host header whenever Symfony's framework.trusted_hosts setting is not configured (the default). An attacker who controls any other application registered with the same CAS server can replay a victim's ticket against the Symfony application, with a spoofed Host header, and be authenticated as that victim.

Resolution

A new required service_url configuration option is introduced on Cas2Handler. The CAS service parameter sent to the validation endpoint is now built from this configured URL instead of being derived from the request's Host header, preventing cross-service ticket replay via Host header spoofing.

The patch for this issue is available here for branch 7.4.

Credits

Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and Nicolas Grekas for providing the fix.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`symfony/security-http`	≥ 7.1.0&&< 7.4.12	7.4.12`composer require symfony/security-http:^7.4.12`
🐘Packagist	`symfony/security-http`	≥ 8.0.0&&< 8.0.12	8.0.12`composer require symfony/security-http:^8.0.12`
🐘Packagist	`symfony/symfony`	≥ 7.1.0&&< 7.4.12	7.4.12`composer require symfony/symfony:^7.4.12`
🐘Packagist	`symfony/symfony`	≥ 8.0.0&&< 8.0.12	8.0.12`composer require symfony/symfony:^8.0.12`

Affected Products

1 product · 2 configurations

Application

symfonysensiolabs

≥ 8.0.0 && < 8.0.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/security-http, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/security-http to 7.4.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j8gj-9rm5-4xhx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

`Cas2Handler` builds this `service` parameter from `Request::getSchemeAndHttpHost()`, which reflects the attacker-controlled HTTP `Host` header whenever Symfony's `framework.trusted_hosts` setting is not configured (the default). An attacker who controls any *other* application registered with the same CAS server can replay a victim's ticket against the Symfony application, with a spoofed `Host` header, and be authenticated as that victim. ### Resolution A new required `service_url` configuration option is introduced on `Cas2Handler`. The CAS `service` parameter sent to the validation endpoi

O3 Security · Impact-Aware SCA

Is GHSA-j8gj-9rm5-4xhx in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works