GHSA-g3rh-rrhp-jhh9 is a low-severity (CVSS 3.1) Improper Input Validation vulnerability in symfony/symfony. A fix is available for symfony/symfony — see the affected versions and patch details below.
Symfony has an incorrect response from Validator when input ends with `\n`
Exploitation Status
No confirmed exploitation observed yet
- 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-g3rh-rrhp-jhh9.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-g3rh-rrhp-jhh9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
symfony/symfony🐘symfony/symfony🐘symfony/symfony🐘symfony/validator🐘symfony/validator🐘symfony/validatorReal-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
Description
It is possible to trick a Validator configured with a regular expression using the $ metacharacters, with an input ending with \n.
Resolution
Symfony now uses the D regex modifier to match the entire input.
The patch for this issue is available here for branch 5.4.
Credits
We would like to thank Offscript for reporting the issue and Alexandre Daubois for providing the fix.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | symfony/symfony | all versions | 5.4.43composer require symfony/symfony:^5.4.43 |
| 🐘Packagist | symfony/symfony | ≥ 6.0.0&&< 6.4.11 | 6.4.11composer require symfony/symfony:^6.4.11 |
| 🐘Packagist | symfony/symfony | ≥ 7.0.0&&< 7.1.4 | 7.1.4composer require symfony/symfony:^7.1.4 |
| 🐘Packagist | symfony/validator | all versions | 5.4.43composer require symfony/validator:^5.4.43 |
| 🐘Packagist | symfony/validator | ≥ 6.0.0&&< 6.4.11 | 6.4.11composer require symfony/validator:^6.4.11 |
| 🐘Packagist | symfony/validator | ≥ 7.0.0&&< 7.1.4 | 7.1.4composer require symfony/validator:^7.1.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for symfony/symfony, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update symfony/symfony to 5.4.43 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3rh-rrhp-jhh9 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g3rh-rrhp-jhh9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-g3rh-rrhp-jhh9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-g3rh-rrhp-jhh9 in your dependencies?
O3 Security finds GHSA-g3rh-rrhp-jhh9 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.